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

Use the Poolside Agent CLI to work with agents from the terminal, run one-shot tasks in scripts and automation, or connect Poolside to ACP-compatible editors. The CLI has three main interfaces:
InterfaceCommandWhat it does
Interactive modepoolInteractive terminal sessions
Automated modepool execOne-shot tasks and automation
Editor integrationpool acpConnect ACP-compatible editors to the agent
If you have not installed or authenticated the CLI yet, start with Install Poolside Agent CLI.

​
Interactive mode

Run pool to open a terminal session with the agent: 
pool
The agent can read your code, run commands, and write files. It asks for approval before taking action. Use this when you expect to go back and forth by refining the task, reviewing changes, or switching modes as you go. Start in a specific directory: 
pool -C /path/to/project
Resume a previous session: 
pool -r
See Interactive mode for the full list of options and session controls.

​
Automated mode

Run pool exec to send a single prompt and exit: 
pool exec -p "What does this codebase do?"
Use this for scripts, CI pipelines, and one-off tasks. See Automated mode for the full list of options and flags.
If you previously used non-interactive flags on pool, such as pool -p, use pool exec instead.

​
Editor integration

To use Poolside in an editor or client without a native Poolside extension, configure the editor to use pool acp, the Agent Client Protocol (ACP) server. Supported editors include Zed, JetBrains, Neovim, and others that implement ACP. For example: 
pool acp setup --editor zed
If you use VS Code or Visual Studio, use the native Poolside Assistant integration instead. See Editor integration (ACP) for setup instructions and other editors.
For pool CLI bugs and feature requests, open an issue on GitHub.