Skip to main content
Run pool exec to send a single prompt and exit when the task is complete. Use this for scripts, CI pipelines, and one-off tasks where you don’t need a back-and-forth. For interactive work, see Work from the terminal instead.
This documentation describes Poolside Agent CLI v1.0.13. Check your version with pool --version. To update, exit any active session and run pool update from your terminal. See Poolside Agent CLI releases on GitHub for release history.

Basic usage

In a non-interactive environment without credentials saved by pool login, choose how you access Poolside and set the variables shown.
To choose a model instead of using the default, also set POOLSIDE_STANDALONE_MODEL to its model ID.
The remaining examples assume that you signed in with pool login or set the required environment variables. Pass a prompt inline:
Read the prompt from a file:
Pipe the prompt from standard input:
Use - to read from standard input when combining with other flags:

Pass MCP server input variables

If an MCP server needs input from environment variables, start pool exec with those variables set:

Run in a specific directory

By default, pool exec uses your current directory. Use -d to point it somewhere else:

Continue from a previous run

Resume from the last run:
Resume a specific run by ID:
To find recent run IDs, use pool history logs.

Output format

By default, pool exec prints Markdown. Use -o json for newline-delimited JSON:
JSON mode prints event-style records. Common types:
  • reasoning: Raw model reasoning
  • thought: Agent message text
  • toolCall: Tool invocations and arguments
  • toolCallResult: Tool results
  • oauth_url: Browser authentication required
Use JSON mode when another tool needs to consume the output.

Run without approval prompts

Use --unsafe-auto-allow when you want pool exec to run in automated mode without approval prompts:
Use this only in trusted non-interactive environments. Explicit deny rules still apply. On a Poolside deployment, --unsafe-auto-allow requires the Auto Approve Commands permission. For persistent approval rules, path rules, and settings.yaml locations, see Permissions.

Override sandbox usage

Use --sandbox required to require a configured sandbox for the run:
Use --sandbox disabled only when you want to run without a configured sandbox.