The paperctl CLI runs locally and captures supported agent sessions to paper console. This page is the map of the CLI docs — what the pieces are and which page gets you to your outcome. For an end-to-end walkthrough, see the Quickstart. Setting up with a coding agent? Point it at papercompute.com/start.md — an agent-followable runbook of the setup steps.
The pieces
paperctl— the command you run: install, sign in, launch agents, list and search sessions.paperd— the local daemonpaperctlsets up after you authenticate. It routes agent traffic and uploads sessions in the background. Check it withpaperctl status; start it withpaperctl init.paper console— where captured sessions land: console.papercompute.com.
Supported agents: Claude Code, Codex, and Pi, each launched with paperctl start <agent> or automatically via shell routing.
Set up
- Install paperctl
- Authenticate
- Capture with Claude Code, Codex, or Pi
- Optional but recommended: automatic shell routing, so plain
claude,codex, andpialways capture
Work with sessions
- List sessions — see what’s been captured
- Inspect a session — one session’s summary
- Search session history — find past work by meaning
- Export session data — pull sessions out as NDJSON
Common commands
| Task | Command |
|---|---|
| Start Claude Code through paper | paperctl start claude |
| Start Codex through paper | paperctl start codex |
| Start Pi through paper | paperctl start pi |
| Check proxy status | paperctl status |
| View logs | paperctl logs --follow |
| Switch orgs | paperctl org select |
| Add a teammate | paperctl org membership add [email protected] |
| Search your sessions | paperctl search "..." |
| List recent sessions | paperctl sessions list |
| Update the CLI | paperctl upgrade |
Every command, flag, and output shape: CLI command reference. Gateway and backend configuration for teams: Custom backends. Setup issues: Troubleshooting.