Until this release, using Atlarix meant a window beside your editor: the desktop app, or since 15.0 the CLI in a terminal. With 15.4.0 the agent moves into the editor itself. One extension for VS Code and the editors built on it — Cursor, Kiro, Windsurf, VSCodium — carries the same agent as the app and the CLI, and Zed and JetBrains IDEs run it through the Agent Client Protocol. This post is what you get and how to start.
Install it
Search for Atlarix in your editor's Extensions view, or install it from the Visual Studio Marketplace (VS Code) or Open VSX (Cursor, Kiro, Windsurf, VSCodium). There are builds for macOS, Windows and Linux on Intel and ARM, and the extension carries its own copy of the Atlarix CLI, so there is nothing else to install. Open the Atlarix view (the ant in the activity bar, or ⌘⌥A / Ctrl+Alt+A) and sign in the first time.
Every mode, any model
The message box has the mode: Build changes code and runs commands, Explore reads and answers without changing anything, Plan writes a plan you can read before anything happens, Debug chases a failure to its cause, Review reads a change and reports what is wrong with it. Just under it is the model: Atlarix Auto, which picks a model for each step, the Atlarix Core models, or any model from your own API key — OpenAI, Anthropic, Google, DeepSeek, OpenRouter and the rest. The picker is the same list the app and CLI show.
Edits you approve in the editor's own diff
When the agent wants to change a file, the editor opens its own side-by-side diff with the proposed version before anything is written. Yes applies it, No leaves the file alone, and Always stops asking for that kind of change in this workspace. Commands wait for you the same way. You are reading the change in the tool you already trust for reading changes.
Plans you can watch being built
In Plan mode the plan appears in its own panel with a checklist of steps. Build it switches to Build and carries it out, and the panel stays on screen while it works: each step goes from ☐ to ◐ to ☑, the header counts them off, and it says Built at the end. You can see where the work is without reading the transcript.
Context without copy-paste
Select code and press ⌘⌥L (Ctrl+Alt+L) to add it to the chat with its file and lines; type @ to attach a file; the + button attaches images. The model's thinking streams into a fold above its answer, so you can watch it reason and close it when the answer starts.
Your Chrome, your other sessions
With the Atlarix Chrome extension installed, the agent in your editor can open pages in your own Chrome — signed in as you — to test what it just built. Every Atlarix session can message every other one: the app, the CLI, Chrome or another editor can hand your editor a task, and it arrives as a card and is answered there. /editor in the CLI moves a terminal chat into your editor; the ⋯ menu in the editor moves it back to the app or a terminal.
Your account in the panel
⋯ → Account, usage and billing shows your plan, credit and this chat's usage, with Get Pro, Add credit and Sign out; your own provider keys; and the MCP servers in this folder, which you can test, switch off or add. Come back after a few minutes away and one line recaps where the chat stands; turn that off in the same menu.
Zed and JetBrains IDEs
Zed and JetBrains IDEs speak the Agent Client Protocol natively, so they run Atlarix's CLI as their agent with no plugin: atlarix acp. Building a plan switches the editor's mode picker, the plan shows as the editor's own plan list, and file links open at the line. The editors guide has the settings for both.
What it costs
Installing the extension is free. Your own API keys cost nothing through Atlarix — you pay your provider directly. Atlarix Core models are paid from Pro or pay-as-you-go credit, the same balance as the app and CLI.
Chats you start in the editor show up in the app and the CLI, and the other way round: it is one agent with one history, wherever you happen to be typing. Install it from the Marketplace or Open VSX, and see the editors guide for everything else.
Originally published at atlarix.dev.
Top comments (0)