Transcripto

transcripto

**your coding agents keep a transcript of every session. it is the most valuable dataset you own, and you cannot scroll back far enough to read it. transcripto indexes it, keeps only the turns you actually typed, and grades them.**

one command, no account, no signup, no cloud. it reads files that are already on your disk and never opens a socket.

uvx transcripto coach

three harnesses, one instrument

transcripto coach                     # Claude Code, ~/.claude/projects
transcripto coach --harness codex     # Codex, ~/.codex
transcripto coach --harness cursor    # Cursor, ~/.cursor/projects/*/agent-transcripts

**Authorship is not the same gate in all three, and the tool says so rather than pooling them.** Claude Code stamps `promptSource: typed`, which is the measured-reliable signal: about 95% of raw `type: user` records are not the operator at all. Cursor has no such field. Its one honest equivalent is the `` wrapper it puts around a submitted prompt, which injected and tool-result records do not carry. That is a weaker signal and it is labelled weaker.

`trace` — what actually happened after you asked

`ask` shows what you typed. `find` shows what a file went through. Neither answers the question that matters after the fact: **you asked for X, did anything durable happen?**

transcripto trace "the gate"

It walks each of your matching prompts forward inside its own session and lists the writes and edits that followed, stopping at your next prompt so one turn cannot claim the next turn's work. Green dot = something durable landed. Red = nothing was touched.

**Honest limit:** a write following a prompt in the same session is CO-OCCURRENCE, not proof the write was caused by that prompt or that it was correct. Same proxy `coach` uses, labelled the same way.

what you get back

this is a real run on one machine, pasted unedited, 2026-08-28:

  YOUR PROMPT HABITS, GRADED   (offline, your machine onl