Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.poolside.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

You can use Poolside in editors that do not have a native Poolside extension by running pool acp. This Agent Client Protocol (ACP) server works with Zed, JetBrains, Neovim, and other editors that support ACP. If you use VS Code or Visual Studio, use the native Poolside Assistant integration instead of ACP.

​
Capabilities

Poolside ACP supports the following capabilities when the editor client exposes them:
  • To-do lists
  • Plan mode
  • Skills
  • AGENTS.md
  • Resume saved sessions when the editor supports session history
  • Change modes and models when the editor supports ACP session configuration
  • Use slash commands when the editor supports them

​
Set up the Zed editor

pool acp setup --editor zed
This writes Poolside agent configuration to ~/.config/zed/settings.json. For more information, see Zed documentation. If you prefer to configure Zed manually, add the following configuration to ~/.config/zed/settings.json: 
{
  "agent_servers": {
    "Poolside": {
      "command": "pool",
      "args": ["acp"],
      "type": "custom"
    }
  }
}
After you configure Zed, restart it and select Poolside from the agent picker.

​
Set up the JetBrains IDE

pool acp setup --editor jetbrains
This writes configuration to ~/.jetbrains/acp.json. For more information, see JetBrains documentation. If you prefer to configure JetBrains manually, add the following configuration to ~/.jetbrains/acp.json: 
{
  "agent_servers": {
    "Poolside": {
      "command": "pool",
      "args": ["acp"]
    }
  }
}
After you configure JetBrains, restart the IDE and select Poolside from the agent or assistant picker.

​
Set up other editors

For editors without automated setup, point the editor’s ACP configuration at pool acp: 
{
  "command": "pool",
  "args": ["acp"]
}
To pass flags to the ACP server, add them to the args array: 
{
  "command": "pool",
  "args": ["acp", "--reasoning", "high"]
}
Use reasoning control only with models behind OpenRouter or another provider that accepts the OpenRouter-style reasoning field. If the underlying model connects directly to the OpenAI Chat Completions API at https://api.openai.com/v1/chat/completions, requests that include the reasoning field fail because OpenAI rejects the field.For Claude 4.6 models through OpenRouter, effort settings other than none are ignored. OpenRouter uses adaptive thinking automatically for those requests.
If an MCP server expects KEY, make sure your editor starts pool acp with KEY set.

​
Set up Neovim with CodeCompanion

If you use Neovim with the codecompanion.nvim plugin, configure Poolside as an ACP-backed adapter: 
{
    "olimorris/codecompanion.nvim",
    dependencies = {
        "nvim-lua/plenary.nvim",
        "nvim-treesitter/nvim-treesitter",
    },
    opts = {
        strategies = {
            chat = { adapter = "poolside" },
            inline = { adapter = "poolside" },
        },
        adapters = {
            poolside = function()
                return {
                    name = "poolside",
                    formatted_name = "Poolside",
                    type = "acp",
                    commands = {
                        default = { "pool", "acp" },
                    },
                }
            end,
        },
    },
}

​
Modes

ModeIDWhat it does
Always askdefaultPrompts for approval on first use of each tool
Accept editsaccept-editsAuto-approves workspace file reads and writes, then prompts for everything else
Allow allalways-allowApproves tool actions automatically
PlanplanPlans changes without modifying your codebase
Mode switching depends on your editor client. If the editor does not expose ACP session modes, you may not be able to change modes from the UI.

​
Slash commands

Poolside makes these slash commands available to compatible ACP clients at session start. They may appear in a command picker or autocomplete menu, or you can type them directly into the prompt if your editor passes slash commands to the ACP server.
CommandWhat it does
/planSwitch to plan mode
/clearClear conversation history and free up context
/shareGet the trajectory viewer URL for the current session when trajectory sharing is available
/usageShow token usage for the current session
/skillsRefresh and list available skills
/debug:clear-local-sessionsDelete 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-edits and plan. Your editor must expose those controls for you to switch modes in the UI.
  • Model selection: Poolside ACP exposes model configuration separately from --reasoning. In standalone mode, selection is limited to the default standalone configuration. 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: 
pool acp logs -f
pool acp logs --pretty
Common issues:
  • pool not found: Add pool to your PATH or 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.