Add chat tip to open the Sessions Window

[Copilot]

Adds a top-level entry point from VS Code into the Sessions window via the chat tip system.

New tip.openSessionsWindow entry in TIP_CATALOG that renders a clickable command link:

Tip: Try the Sessions Window to run multiple agents simultaneously and manage your coding sessions.

• Gated to non-stable builds (ProductQualityContext), non-sessions windows (IsSessionsWindowContext), and agent mode only
• Auto-dismissed on link click via dismissWhenCommandsClicked
• Permanently excluded after workbench.action.openSessionsWindow has been executed
• QoL tier, so it appears after foundational onboarding tips

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• redirector.gvt1.com
  • Triggering command: /proc/self/exe /proc/self/exe --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --crashpad-handler-pid=7141 --enable-crash-reporter=7e777c04-de5c-4838-ba46-0780714f3424,no_channel --user-data-dir=/tmp/vscode-tests-1774937841435 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,10101467747417854436,3149208591223126436,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708989122997041 (dns block)
  • Triggering command: .build/electron/code-oss .build/electron/code-oss test/unit/electron/index.js --crash-reporter-directory=/tmp/vscodecrash --run src/vs/workbench/contrib/chat/test/browser/chatTipService.test.ts (dns block)
  • Triggering command: /proc/self/exe /proc/self/exe --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --crashpad-handler-pid=7287 --enable-crash-reporter=7e777c04-de5c-4838-ba46-0780714f3424,no_channel --user-data-dir=/tmp/vscode-tests-1774937863098 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,3054058367138632310,3362019481948340825,262144 --enable-features=PdfUseShowSaveFilePicker --disable-features=LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708989122997041 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[bpasero]

cc @bamurtaugh @lostintangent

[Copilot]

Pull request overview

Adds a new Chat Tip entry that promotes the Sessions Window as a top-level entry point from within VS Code chat, intended to help users discover multi-agent workflows and sessions management.

Changes:

• Adds tip.openSessionsWindow to TIP_CATALOG with a command link to workbench.action.openSessionsWindow.
• Gates tip visibility via context keys (non-stable product quality, not already in Sessions Window, Agent mode).
• Ensures the tip is excluded/dismissed after the Sessions Window command is executed/clicked.

[Copilot]

workbench.action.openSessionsWindow appears to be registered only in the electron-browser contribution (search shows no browser/web registration). Since this tip is in the shared browser tip catalog, it can surface in web builds and render a command link that does nothing. Consider gating the tip with IsWebContext.negate() (or moving this tip to an electron-only catalog) so it only appears where the command is available.