You know the feeling when you start a Claude Code session, step away, come back to "All done!" and have no idea what actually changed or why.

Claude Code's transcript shows the agent working. But it doesn't really show you what changed, which assumptions it made, or whether anything was actually verified.

I built TraceBack to answer that. It hooks into Claude Code's hook system and turns a session into something reviewable:

* **Net-change diff per file** — true before/after with the agent's own reasoning attached
* **Decision ledger** — surfaces silent judgment calls like "I'll assume the config stays JSON" before they calcify across 3 files
* **Guards** — block dangerous calls automatically (rm -rf, git push main, edits outside project) before they run
* **Breakpoints** — actually pause a running agent mid-session and redirect it

Zero cloud, zero API keys, runs fully local inside VS Code.

Check out 1-min demo

Would love feedback -> especially on the guards and redirect features which I think are the most underrated part.

GitHub: [https://github.com/madiyarzm/TraceBack](https://github.com/madiyarzm/TraceBack) (pls star me :))

VS Code extensions marketplace: [https://marketplace.visualstudio.com/items?itemName=madiyarzhunussov.traceback-ai](https://marketplace.visualstudio.com/items?itemName=madiyarzhunussov.traceback-ai)

I built a VS Code extension that shows you what Claude Code actually did, why, and whether you can trust it