paseo-companion
Paseo Companion
Paseo is a daemon-managed CLI for launching, observing, and steering AI coding agents. Every agent gets a stable ID that serves as the handle for all subsequent operations — follow-ups, logs, waiting, archiving.
paseo <command> [options]
Typical workflows
Run a single task and wait for completion
paseo run "implement the new auth flow"
Blocks until the agent finishes. Add --wait-timeout 30m to cap the wait.
Send a follow-up to the same agent
Reuse before relaunch — if an agent already exists for related work, continue it:
paseo send <id> "now add tests for the new endpoint"
<id> accepts a unique prefix or the agent name, not just the full UUID.
Run multiple agents in parallel
Detach agents, do other work, then join:
api_id=$(paseo run -d --json "implement the API" | jq -r .id)
ui_id=$(paseo run -d --json "implement the UI" | jq -r .id)
# ... do other work ...
paseo wait "$api_id"
paseo wait "$ui_id"
Isolate work in a git worktree
paseo run --worktree feature-x "implement feature X"
paseo run --worktree experiment-y --base develop "try approach Y"
Iterate until tests pass
paseo loop run "fix the failing tests" \
--verify-check "npm test" \
--max-iterations 10
Use --verify "<prompt>" for an agent-based verifier instead of a shell command.
Monitor a running agent
paseo logs <id> -f # stream live output
paseo attach <id> # interactive stream (Ctrl+C detaches, doesn't stop)
paseo inspect <id> # detailed metadata snapshot
List and manage agents
paseo ls # active agents
paseo ls -a # include archived
paseo stop <id> # interrupt a running agent
paseo archive <id> # soft-delete
paseo delete <id> # hard-delete
Common options
--provider codex/gpt-5.4 # pick provider/model
--cwd /path/to/repo # set working directory
--host 10.0.0.8:6767 # target a remote daemon
--json # machine-readable output
-d # detach (return immediately, print agent ID)
--prompt-file ./task.md # read prompt from file (for long/complex prompts)
--image screenshot.png # attach an image to the prompt
Command map
| Goal | Command |
|---|---|
| Launch and wait | paseo run "PROMPT" |
| Launch detached | paseo run -d "PROMPT" |
| Continue an agent | paseo send <id> "PROMPT" |
| Wait for completion | paseo wait <id> |
| Stream logs | paseo logs <id> -f |
| Attach interactively | paseo attach <id> |
| List agents | paseo ls [-a] |
| Stop/archive/delete | `paseo stop |
| Target remote daemon | add --host <ip>:<port> |
When to read references
| You need to... | Read |
|---|---|
| Inspect, stop, archive, delete agents; update metadata or labels | references/agent-management.md |
| Discover providers/models, select a provider, switch modes, enable thinking | references/providers-and-modes.md |
| Use git worktrees for isolation, manage Paseo-created worktrees | references/worktree-and-cwd.md |
| Set up verification loops or recurring scheduled tasks | references/loop-and-schedule.md |
| Create persistent terminals, send keystrokes, capture output | references/terminal.md |
| Set up inter-agent chat rooms or handle permission requests | references/chat-and-permit.md |
| First-time setup, daemon start/stop/restart, connect to remote daemon | references/daemon-and-onboarding.md |
| Script/automate Paseo output, JSON/YAML formats, schema validation | references/output-formats.md |
Non-negotiables
- Reuse before relaunch. If an agent already exists for related work,
paseo sendto it — don't spin up a new one. - Wait, don't poll. Never loop on
paseo ls/paseo inspect. Usepaseo wait <id>(blocks efficiently) orpaseo logs <id> -f(streams). - Timeout doesn't stop. If
waittimes out, the agent is still running. Usepaseo stop <id>to actually interrupt. - Quote prompts. For multi-line or escape-heavy prompts, use
--prompt-file.
More from atomlink-ye/my-claude-plugins
debug-workflow
Unified debug workflow skill for real-world issue reproduction, especially browser/UI/Web3 problems that need Playwright, shared Chrome/CDP, or agent-wallet. Use this whenever the user wants to confirm whether a workflow can reproduce real issues from walkthrough docs, issue lists, QA notes, or live bug reports. Start with the debug index, route to the right lane, and prefer deterministic local reproduction over fragile preview environments.
11task-iteration
Orchestrate end-to-end feature implementation from an exec-plan document. Use this whenever the user wants a structured Plan → Generate → Evaluate loop for a feature. It keeps planning and acceptance in Claude, pushes bounded coding/test execution to OpenCode companion sessions, reuses warm sessions across fix rounds, and gates completion on independent evaluation plus an advisory review.
11google-workspace
Read, create, and edit Google Workspace documents using the `gws` CLI. Use this skill whenever the user mentions Google Docs, shares a docs.google.com URL, references a Google Doc ID, or wants to read/write/create Google documents. Also trigger on 'GDoc', 'gdoc', 'Google Doc', 'gws docs', or any Google Workspace document operation. Will expand to cover Drive, Sheets, Gmail, Calendar, and other GWS services.
11opencode-orchestrator
Aggressively load this skill BEFORE any delegation decision — explore, plan, implement, review, adversarial second-opinion, bounded investigation, or any medium/heavy coding request. Also triggers for manager-vs-executor routing, OpenCode session reuse, multi-step coding orchestration, and work that likely exceeds 10 tool calls, 5 files, or repeated read/edit/test loops. When the live snapshot below shows OpenCode serve is reachable, this skill's routing takes precedence over the caller's generic delegation defaults across every delegated action, not only bounded coding execution. If serve is unreachable, fall back silently to the caller's defaults.
11opencode-companion
OpenCode runtime companion. Load for OpenCode task/review/status/serve/rescue requests, session IDs, timeout recovery, attach/resume decisions, background jobs, and result forwarding.
11daytona-companion
Daytona sandbox companion. Load for sandbox up/status/push/exec/pull/down/preview/smoke-test requests, adopting existing sandboxes, artifact and git-sync workflows, and sandbox environment variables or secrets.
11