* feat: create versioned resources for windows setup
* chore: use inno_updater to remove old installation
* chore: remove old installation as part of setup
* chore: update explorer-command
* chore: prefer session-end
* chore: uninst delete updating_version
* chore: make session-ending write synchronous
* chore: cleanup updateService.win32.ts
* chore: invoke inno_updater gc path for non background update
* chore: move session-end path to runtime
* chore: use commit for updating_version
* chore: fix invalid string
* chore: set appUpdate path
* chore: update inno_updater
* chore: empty commit for testing
* chore: some cleanups
1) Check for session-ending flag in appx and tunnel callsites
2) Move gc for background update to cleanup phase in updateservice
3) Set update state to ready when there is a running inno_setup
* chore: disallow same version update
* chore: disallow application launch in the middle of update
* chore: empty commit for testing
* chore: bump inno_updater
* chore: empty commit for testing
* chore: move gc to update startup
* chore: move feature behind insider only check
* chore: bump inno_updater
* chore: bump explorer-command
* fix: build
* fix: gc for background update in system setup
* chore: create separate cli entrypoints for build
* fix: check for setup mutex created by inno
* chore: remove problematic updatingVersionPath deletion
* chore: remove redundant update check
* chore: bump inno_updater
* chore: fix build
* chore: bump inno updater
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
* Allow modals in automation
This allows for the opt-in behavior of allowing dialogs while using automation.
When opted in, we also switch over to using custom dialogs & the simple file picker so that the automation can control it.
This was added so that we can do auth flows, which uses dialogs. Now we will be able to complete an auth flow (with the help of the user in the browser) and automate interacting with chat via the development MCP server.
* Instead use custom for smoke tests
* Go back to command but have a context key for automation
* Workaround terminal smoke tests
