More Updates
- paper is now paperctl — and installs no longer need sudoJul 23, 2026
- See models in session tableJul 23, 2026
- Every session shows its outcomesJul 17, 2026
- paperctl sessions in the CLIJul 14, 2026
- Export your session dataJul 11, 2026
- Delete sessions from the consoleJul 10, 2026
- Insights dashboard for spend and session healthJun 30, 2026
- Turn dead tokens into skillsJun 26, 2026
- paper now works with CodexJun 23, 2026
- Richer session detailsJun 16, 2026
- Changelog goes liveJun 10, 2026
- paperctl CLI is now in alphaJun 09, 2026
paper now works with Codex
paper started out capturing Claude. Now it captures Codex too — on a fresh org, paperctl start codex just works and the sessions stream into paper console.
paper started with one agent: Claude. Today it works with Codex too.
Your team’s Codex sessions stream into paper console like any other agent, with the
same per-turn cost, token, and activity detail you already get from Claude. On a fresh
org there’s nothing to wire up — your users just run:
paperctl start codexWhether they’re on a ChatGPT plan or bringing their own OpenAI key, the route is
already there. paper provisions two transparent Codex backends under your default
gateway automatically:
- ChatGPT plan — Codex forwards the OAuth token it already holds. No API key to create, store, or rotate.
- Per-user OpenAI key — paper passes each caller’s
OPENAI_API_KEYstraight through to OpenAI.
paper picks the right one by the shape of each request, so the same command works for everyone. The one path that takes setup is a team-managed key — a single shared OpenAI key paper stores once and injects for everyone on a gateway. Those commands, and the full backend reference, are in the custom backend docs.