--- title: CLI description: "Paseo CLI reference: manage agents, daemons, permissions, and worktrees from your terminal." nav: CLI order: 3 category: Getting started --- # CLI The Paseo CLI lets you manage agents from your terminal. It's the same interface exposed by the daemon's API, so anything you can do in the app you can do from the command line. > **Agent orchestration:** You can tell coding agents to use the Paseo CLI to spawn and manage other agents. This enables multi-agent workflows where one agent delegates subtasks to others and waits for results. ## Quick reference ```bash paseo run "fix the tests" # Start an agent paseo ls # List running agents paseo attach # Stream agent output paseo send "also fix linting" # Send follow-up task paseo logs # View agent timeline paseo stop # Stop an agent ``` ## Running agents Use `paseo run` to start a new agent with a task: ```bash paseo run "implement user authentication" paseo run --provider codex "refactor the API layer" paseo run --detach "run the full test suite" # background paseo run --worktree feature-x "implement feature X" paseo run --output-schema schema.json "extract release notes" paseo run --output-schema '{"type":"object","properties":{"summary":{"type":"string"}},"required":["summary"]}' "summarize release notes" ``` The `--worktree` flag creates the agent in an isolated git worktree, useful for parallel feature development. Use `--output-schema` to return only matching JSON output. You can pass a schema file path or an inline JSON schema object. This mode cannot be used with `--detach`. By default, `paseo run` waits for completion. Use `--detach` to run in the background. ## Listing agents ```bash paseo ls # Running agents in current directory paseo ls -a # Include completed/stopped agents paseo ls -g # All directories paseo ls -a -g --json # Full list as JSON ``` ## Streaming output Use `paseo attach` to stream an agent's output in real-time: ```bash paseo attach abc123 # Attach to agent (Ctrl+C to detach) ``` Agent IDs can be shortened, `abc` works if it's unambiguous. ## Sending messages Send follow-up tasks to a running or idle agent: ```bash paseo send "now run the tests" paseo send --image screenshot.png "what's wrong here?" paseo send --no-wait "queue this task" ``` ## Viewing logs ```bash paseo logs # Full timeline paseo logs -f # Follow (streaming) paseo logs --tail 10 # Last 10 entries paseo logs --filter tools # Only tool calls ``` ## Waiting for agents Block until an agent finishes its current task: ```bash paseo wait paseo wait --timeout 60 # 60 second timeout ``` Useful in scripts or when one agent needs to wait for another. ## Permissions Agents may request permission for certain actions. Manage these from the CLI: ```bash paseo permit ls # List pending requests paseo permit allow # Allow all pending for agent paseo permit deny --all # Deny all pending ``` ## Agent modes Change an agent's operational mode (provider-specific): ```bash paseo agent mode --list # Show available modes paseo agent mode bypass # Set bypass mode paseo agent mode plan # Set plan mode ``` ## Daemon management ```bash paseo daemon start # Start the daemon paseo daemon start --web-ui # Start and serve the bundled web UI paseo daemon status # Check status paseo daemon stop # Stop the daemon ``` Use `PASEO_HOME` to run multiple isolated daemon instances. ## Connecting to a remote daemon `--host` accepts either a local target (`host:port`, a unix socket, or a Windows pipe) or a pairing offer URL, the same `https://app.paseo.sh/#offer=...` link the mobile app uses for QR pairing. With an offer URL the CLI connects through the Paseo relay with end-to-end encryption, so you can drive a daemon on another machine without exposing it to the network. Get an offer URL from the daemon you want to control: ```bash paseo daemon pair --json # prints { url, qr, ... } ``` Use it from anywhere: ```bash paseo ls --host 'https://app.paseo.sh/#offer=eyJ2IjoyLC...' paseo run --host "$OFFER_URL" "fix the failing tests" ``` You can also set it once via `PASEO_HOST` instead of passing `--host` on every command. ## Multi-agent workflows The CLI is designed to be used by agents themselves. You can instruct an agent to spawn sub-agents for parallel work: ```bash # Agent A spawns Agent B and waits for it paseo run --detach "implement the API" --name api-agent paseo wait api-agent paseo logs api-agent --tail 5 ``` Simple implement + verify loop: ```bash # Requires jq while true; do paseo run --provider codex "make the tests pass" >/dev/null verdict=$(paseo run --provider claude --output-schema '{"type":"object","properties":{"criteria_met":{"type":"boolean"}},"required":["criteria_met"],"additionalProperties":false}' "ensure tests all pass") if echo "$verdict" | jq -e '.criteria_met == true' >/dev/null; then echo "criteria met" break fi done ``` This pattern enables hierarchical task decomposition, a lead agent can break down work, delegate to specialists, and synthesize results. ## Output formats Most commands support multiple output formats for scripting: ```bash paseo ls --json # JSON output paseo ls --format yaml # YAML output paseo ls -q # IDs only (quiet) ``` ## Global options - `--host `, connect to a different daemon (`host:port`, unix socket, or `https://app.paseo.sh/#offer=...` for relay). See [Connecting to a remote daemon](#connecting-to-a-remote-daemon). - `--json`, JSON output - `-q, --quiet`, minimal output - `--no-color`, disable colors