For a list of editors and tools that support ACP, check out the ACP progress report.
Configure
To use Symbiotic Code via ACP, configure your editor to run thesymbiotic acp command.
The command starts Symbiotic Code as an ACP-compatible subprocess that communicates with your editor over JSON-RPC via stdio. The project directory is provided by your editor when it opens a session.
If you aren’t logged in, the editor offers a Login with symbiotic option, which runs symbiotic auth login.
Below are examples for popular editors that support ACP.
Zed
Add to your Zed configuration (~/.config/zed/settings.json):
~/.config/zed/settings.json
agent: new thread action in the Command Palette.
You can also bind a keyboard shortcut by editing your keymap.json:
keymap.json
JetBrains IDEs
Addacp.json to your JetBrains IDE according to the documentation:
acp.json
Support
Symbiotic Code works the same via ACP as it does in the terminal. The following features are supported:- Built-in tools (file operations, terminal commands, etc.)
- Custom tools and slash commands, including skills, MCP prompts, and
/compact - MCP servers configured in your Symbiotic Code config, plus MCP servers sent by your editor
- Project-specific rules from
AGENTS.md - Custom formatters and linters
- Agents and permissions system: primary agents appear as session modes, and permission prompts are shown by your editor with Allow once, Always allow, and Reject options
- Model and variant selection, and loading, resuming, and forking previous sessions
Slash commands that only exist in the TUI, like
/undo, /redo, and /security-mode, are not available. Sessions use the agent’s configured security_mode, or Balanced by default.The
question tool is disabled by default in ACP. Set SYMBIOTIC_ENABLE_QUESTION_TOOL=1 in the command’s environment if your editor supports interactive question prompts.