Every session your team captures through the paperctl CLI lives in paper console as structured history — not terminal output. Over time, that history is what helps a team understand how AI work actually happens across people, projects, and tools: which prompts produced useful results, where agents got stuck, what cost what, and which workflows are worth repeating.
What you can do in paper console
- Inspect any session — read the full chain of prompts, turns, tool calls, and telemetry for a captured run, plus the author who ran it.
- See outcomes and models at a glance — every session lists the pull requests, repos, and issues it created, linked to the real thing, and the sessions table shows which model ran each session.
- Search and filter — find a specific session, a teammate’s work, every failed run in the last week, or the most expensive sessions of the month.
- See team activity — switch between your own captured runs and your full team’s, and read the aggregate dashboard for spend, agent time, tool calls, and completion rate.
- Switch orgs and gateways — move between organizations and gateways you have access to from the console header.
- Export and delete sessions — download any session as full-fidelity JSONL, bundle the last 30 days into one file, or permanently remove a session and everything it spawned.
- Build a shared record — accumulated history of agent work, ready to share with teammates, compare across projects, and turn into reusable knowledge.
How value compounds
One session → understand specific work
Many sessions → identify patterns
Best sessions → create reusable SkillsOne captured run answers “how did this happen?” — that’s the session detail page. A few weeks of runs answer “where is the time and money going?” — that’s Insights. And the sessions worth repeating become Skills your whole team can reuse.
Find your way around
- Team workspace — the shared session list: filter, sort, scan models, export
- Understand session details — read one run end to end
- Insights — spend and run health across the team
- Skills — turn the best sessions into reusable knowledge
- Manage your team workspace — organizations, members, and visibility
Frequently asked questions
How do sessions get into paper console?+
The paperctl CLI captures them. Run an agent through paperctl start (for example paperctl start claude) and the session is saved to paper console as structured history. See the Quickstart.
Can I see my teammates' sessions?+
Yes. A console workspace shows every session anyone on the team ran. Use the scope filter to switch between your own runs and the whole team's. See the Team workspace.
What's inside a session?+
The full chain of prompts and turns, every tool call, and telemetry — model, tokens, cost, duration, and completion status — plus the teammate who ran it. See Understand session details.