pool acp. This Agent Client Protocol (ACP) server works with Zed, JetBrains, Neovim, and other editors that support ACP.
If your IDE already has a native Poolside Assistant integration, use that instead of ACP.
Set up the Zed editor
~/.config/zed/settings.json. For more information, see Zed documentation.
Set up the JetBrains IDE
~/.jetbrains/acp.json. For more information, see JetBrains documentation.
After running setup for either editor:
- Restart the editor.
- Open the agent or assistant picker.
- Select Poolside.
Set up other editors
For editors without automated setup, point the editor’s ACP configuration atpool acp:
pool acp reads matching environment variables from its own process environment. If an MCP server expects KEY, make sure the editor launches pool acp with KEY set.
Neovim with CodeCompanion
Modes
| Mode | ID | What it does |
|---|---|---|
| Always Ask | default | Prompts for approval on first use of each tool |
| Accept Edits | accept-edits | Auto-approves workspace file reads and writes, then prompts for everything else |
| Always Allow | always-allow | Approves tool actions automatically |
| Plan | plan | Plans changes without modifying your codebase |
/mode <id> if the editor doesn’t expose a mode picker.
Slash commands
Poolside advertises available slash commands to the client when a session starts. They may appear in a command picker or autocomplete menu, or you can type them directly into the prompt.| Command | What it does |
|---|---|
/mode | List available modes or switch modes |
/plan | Switch to plan mode |
/clear | Clear conversation history and free up context |
/share | Get the trajectory viewer URL for the current session |
/usage | Show token usage for the current session |
/skills | Refresh and list available skills |
/debug:clear-local-sessions | Delete locally persisted session history |
Feature parity
The core agent capabilities are close to interactive mode, but exact support depends on the editor client:- Mode selection: Poolside ACP exposes session modes, including
accept-editsandplanwhen available. Your editor must expose those controls for you to switch modes in the UI. - Model selection: Poolside ACP exposes model configuration separately from
--reasoning. With standalone setup, selection is limited to the standalone model. When connected to a Poolside deployment, editors can expose deployment-specific agent or model choices if they support ACP session config options. - Rewind: Poolside ACP supports session rewind, but your editor has to expose that capability.
- Session history: Poolside ACP supports persisted session history through ACP session listing and loading, but some editors do not expose history browsing in the UI.
Troubleshooting
Check ACP logs:poolnot found: Addpoolto yourPATHor use the full path to the binary.- Auth errors in standalone mode: Run
pool setup, then reconnect. - Auth errors when connected to a Poolside deployment: Run
pool login, then reconnect. - Missing mode, history, rewind, or slash command: ACP capabilities depend on both your editor client and your Poolside account access.