feat(mcp): use per-context dashboard for browser_annotate#40689
feat(mcp): use per-context dashboard for browser_annotate#40689Skn0tt wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Instead of spawning the singleton dashboard daemon when browser_annotate is invoked, MCP now lazily opens its own dashboard window per context via Context.ensureDashboard(). MCP owns the lifecycle: the dashboard closes when the context disposes or the client disconnects. The modal dashboard surfaces all sessions (workspace-grouped in the UI) via RegistrySessionProvider, so IdentitySessionProvider is no longer needed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Found a good reason against modal dashboard: It goes against server mode, and we already have reports from people that care about that. microsoft/playwright-cli#325 |
Test results for "MCP"14 failed 6962 passed, 1058 skipped Merge workflow run. |
Summary
browser_annotateno longer spawns the singleton dashboard daemon; instead each MCP context lazily opens its own dashboard window viaContext.ensureDashboard().IdentitySessionProvideris gone.openDashboardForContext→ renamedopenDashboard()).Pushing to CI for early feedback — opening as draft.