A map built from your actual code.
To build the map, the GitHub App copies your repo into a temporary sandbox, reads its structure, and deletes it — your code is never saved to our database. What it keeps is the shape: the modules become nodes, the dependencies between them become edges. External services (Stripe, your queue) show up dashed, so the boundary of your system is obvious at a glance.
- Nodes are the real subsystems in your repo, not a diagram someone drew.
- Edges are the dependencies that actually exist between them.
- Every node carries the decisions, tradeoffs and risks that touch it.
- Read-only, one repo at a time, revoke anytime — private repos stay private.
Rewind the whole system.
The map rebuilds on every merge to your main branch, and every build is kept. Drag the time slider and the diagram becomes what your system looked like then — modules appear and disappear, edges form, and each decision, tradeoff and risk snaps to the moment it entered the codebase.
So you don't just see what your system is — you see how it got there: when a module showed up, when a risk was introduced, when a tradeoff was quietly accepted. It never drifts, because it's rebuilt from what actually shipped, not from a doc someone wrote six months ago.
The why, pinned to the map.
The map is the where; the insights are the why. Backthread reads your agent sessions and git history — commits, PRs, reviews, and the issues linked to your work — and its plugin strips code and command output on your own machine, sending only the plain-English reasoning. One pass turns all of it into decisions, accepted tradeoffs and potential risks — ranked, deduplicated, each with its rationale — and pins each one to the module it touches.
- Decisions — the choices your agent made, and why.
- Tradeoffs — what was accepted to get there, and the cost.
- Risks — what was left behind that's worth a second look.
what leaves your machine, and what we store, is on /security →
This is the substrate. The short list is the point.
You don't have to think about any of this. The map and the timeline run themselves — what you get is a short, ranked feed of what's worth understanding about the code your agents wrote.
See it on your own repo.
One command builds your real map and its decision log, free. Rewind it whenever you want.