Merge remote-tracking branch 'origin/main' into joao/copilot-builtin

Author: joaomoreno

.agents/skills/launch/SKILL.md

@@ -111,19 +111,19 @@ agent-browser snapshot -i
 - Code OSS uses the default user data directory. Unlike VS Code Insiders, you don't typically need `--user-data-dir` since there's usually only one Code OSS instance running.
 - If you see "Sent env to running instance. Terminating..." it means Code OSS is already running and forwarded your args to the existing instance. Quit Code OSS and relaunch with the flag, or use `--user-data-dir=/tmp/code-oss-debug` to force a new instance.
 
-## Launching the Sessions App (Agent Sessions Window)
+## Launching the Agents App (Agents Window)
 
-The Sessions app is a separate workbench mode launched with the `--sessions` flag. It uses a dedicated user data directory to avoid conflicts with the main Code OSS instance.
+The Agents app is a separate workbench mode launched with the `--agents` flag. It uses a dedicated user data directory to avoid conflicts with the main Code OSS instance.
 
 ```bash
 cd <repo-root>  # the root of your VS Code checkout
-./scripts/code.sh --sessions --remote-debugging-port=9224
+./scripts/code.sh --agents --remote-debugging-port=9224
 ```
 
 Wait for the window to fully initialize, then connect:
 
 ```bash
-# Wait for Sessions app to start, retry until connected
+# Wait for Agents app to start, retry until connected
 for i in 1 2 3 4 5; do agent-browser connect 9224 2>/dev/null && break || sleep 3; done
 
 # Verify you're connected to the right target (not about:blank)
@@ -132,7 +132,7 @@ agent-browser snapshot -i
 ```
 
 **Tips:**
-- The `--sessions` flag launches the Agent Sessions workbench instead of the standard VS Code workbench.
+- The `--agents` flag launches the Agents workbench instead of the standard VS Code workbench.
 - Set `VSCODE_SKIP_PRELAUNCH=1` to skip the compile step if you've already built.
 
 ## Launching VS Code Extensions for Debugging