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
Every session shows its outcomes
Session detail pages now show what a session actually produced. Pull requests, repos, GitHub issues, Linear issues, or a plain "no outcome" if it made nothing.
In paper console, every session detail page now has an Outcomes section
under Session Info. It lists what the session produced, linked to the real
thing: pull requests, repositories, GitHub issues, and Linear issues. If the
session produced nothing, it says no outcome plainly instead of leaving you
to scroll the transcript and guess.
An outcome is something the session created, not something it looked at. A session that opened a pull request gets credit for it. A session that merely viewed one doesn’t. The same outcome mentioned twice shows up once.
Live sessions count too. A pull request opened mid-session shows up while the session is still running, so you can follow the link while reviews and QA continue. The section waits until detection has something to say, so a running session is never labeled “no outcome” prematurely.
Open any session to see it. Outcomes sits right under Session Info in the detail panel.