AI Switcher now has a VS Code and Cursor extension
I published the first aisw extension for VS Code and Cursor, making AI coding-agent account switching available from the editor while keeping credentials in the native aisw CLI.
The aisw VS Code and Cursor extension puts account switching, verification, and diagnostics in the editor while leaving credentials with the local aisw CLI.
I published the first aisw VS Code extension. It also works with Cursor, so the same account boundary is available in the editor where many coding-agent sessions now begin.
The reason is simple: switching between work, personal, and client accounts should not require leaving the editor, remembering hidden configuration paths, or copying credential files. The extension is deliberately small. It calls the installed aisw binary, shows the current context and profile in the status bar, and provides quick actions for switching, verification, refresh, and diagnosis. Credentials never pass through the extension.
The native CLI remains the source of truth. That means the extension works with the same profiles, contexts, backups, workspace rules, and provider login flows as the terminal. If the extension is not the right interface for a task, the integrated terminal is always available.
Publishing it was harder than building it#
The code was not the difficult part. Publishing a VSIX through the Microsoft Marketplace was.
The process crosses the Marketplace, Azure DevOps, Microsoft identity, publisher accounts, personal access tokens, and separate marketplace tooling. The documentation is fragmented and the account setup is heavier than the task deserves. For an open-source developer shipping a small extension, this is an unnecessarily poor developer experience. Microsoft should make publishing a signed, repeatable extension release a first-class workflow instead of sending developers through several unrelated systems.
I spent enough time on that plumbing to decide to publish this release manually. That is not the long-term plan. A future release workflow should build, test, package, and publish from a protected release process with auditable credentials. For now, manual publishing is the reliable option while the account and automation path settles.
More people are using aisw than I expected#
The best part is seeing people other than me find aisw useful. I have also been surprised to see developers build small tools and workflows on top of it. That is exactly what I hoped for: a boring, local boundary around account state that other tools can compose with.
Install the extension from the Visual Studio Marketplace, then follow the aisw documentation if you need to set up profiles or workspace rules. The source and issue tracker are on GitHub.