Add a Coding Agent to Zed and JetBrains IDEs With the Agent Client Protocol
Zed and JetBrains IDEs both speak the Agent Client Protocol (ACP): an open protocol between an editor and a coding agent, so the editor provides the chat, the diffs and the approvals, and any agent that implements the protocol can sit behind them. No plugin is involved. Atlarix implements it with one command, atlarix acp. Here is how to add it to each editor.
Install the Atlarix CLI
ACP editors start the agent as a program, so first install the CLI: npm i -g atlarix, brew install amariahak/atlarix/atlarix, or the one-line installers on the CLI page. Check it with atlarix --version.
Zed
Open Zed's settings (~/.config/zed/settings.json) and add Atlarix as an agent server: "agent_servers": { "Atlarix": { "type": "custom", "command": "atlarix", "args": ["acp"] } }. Then open the Agent Panel, start a new thread and choose Atlarix. Sign in when it asks; it opens your browser once.
JetBrains IDEs
In IntelliJ IDEA, PyCharm, WebStorm, GoLand or any other JetBrains IDE with AI Assistant, open the chat's agent menu and choose More Agents → Add Custom Agent. That opens ~/.jetbrains/acp.json; add "agent_servers": { "Atlarix": { "command": "/path/to/atlarix", "args": ["acp"] } } with the full path from which atlarix (macOS, Linux) or where atlarix (Windows). You do not need a JetBrains AI subscription to use an ACP agent.
What you get in the editor
Atlarix's modes — Build, Explore, Plan, Debug, Review — and its models appear in the editor's own mode and model pickers. Edits and commands come to you as the editor's permission prompts before anything changes. In Plan mode the plan shows as the editor's plan list, and building it switches the mode picker to Build. File references in replies open at the line. Past chats load from the editor's history.
Signing in
Atlarix offers two sign-in methods to an ACP editor: a browser sign-in the editor can start for you, and atlarix login in a terminal. Either signs in the CLI on that computer, and the editor's chats then use your account, your models and your own keys.
The same agent everywhere
A chat started in Zed or a JetBrains IDE is an Atlarix session like any other, so it shows up in the Atlarix app and CLI, and other Atlarix sessions can message it. The editor is just one more place to type.
We have also submitted Atlarix to the ACP registry, which Zed and JetBrains read to offer agents with one click; until that is merged, the settings above are the way in. For VS Code, Cursor, Kiro and Windsurf, which do not speak ACP, Atlarix has its own extension — see the editors guide.