Valistry

Docs Optimize Developers

Developers

See how coding sessions end, and try coding reads on one session file before turning it on.

Every figure, and how it is computed

How sessions end
A pull request, a commit, or neither, by team and by tool.
What each person sends
Tokens per request, how sessions start, Opus and cache shares, limits hit and tokens a commit, by person, team or key.
Which tool, which model
The same people on each tool and model, against themselves.
Coding reads, opt-in
What one session file would give: tests run, failed commands repeated, edits redone, how it ended. Read in the browser.

What you do here

  • Open a person for their own page.
  • Group by person, team or API key.
  • Drop a Claude Code session file to see what would be kept.