* vscode mcp: support specifying workspace path; enable restart tool
* fix: include workspace path in launch options for browser
* fix: ensure workspace path is set for tests requiring a workspace
* Address PR review comments: support optional workspace path
* fix: standardize workspace path variable naming in tests
* fix: fallback to rootPath for workspacePath in CI environments
1. the mcp server wasn't working... perhaps due to our js -> ts build move... or a bump in a npm package. Either way, good now.
2. I list out all tools across Copilot CLI & VS Code that would apply in this case... there's some overlap for sure... but I want to make sure we're golden for any renamed tools situations.
* Add a send message tool for automation & mcp
This also sents up the posibility of smoke tests.
* Add demonstrate.md and remove prompt
* add simple notification util
* notif
This enables:
* Playwright video recording
* Starting the Code OSS on server start (for clients like Copilot CLI that don't react to tool list changes)
For #269213
This adds a new eslint rule for `as any` and `<any>({... })`. We'd like to remove almost all of these, however right now the first goal is to prevent them in new code. That's why with this first PR I simply add `eslint-disable` comments for all breaks
Trying to get this change in soon after branching off for release to hopefully minimize disruption during debt week work
This makes sure that closing the window actually closes everything to workaround the macOS behavior of having all windows closed but it's still running.
* First pass at disabling tools that aren't useful for this MCP flow
And enable the multiplexer server
* revert that
* revert that
* revert that
* disable a couple more
* add a start to improve model behavior & rewrite prompt file
* Add another server built on top of our own automation framework
It's a big PR but a lot of this is boiler plate. It's just essentially wrapping our Automation framework in a bunch of tools.
* Lay the foundation for multiplexing
This fixes things for MCP... with a hack. But Playwright is not interested in having interop between Playwright & Playwright MCP atm... so this is the best we can do for now.
So that mcp can use dialogs and let the user answer the dialogs. This is critical for auth.
This also switches to using the custom dialog in electron so that the driver can interact with it.
