It can read your entire codebase. It cannot read why any of it is that way.
The reasoning lives somewhere it can't reach in PR descriptions, in commit messages, in a review thread from March, and mostly in sessions that already ended.
So it re-derives decisions your team made six months ago. Sometimes it re-derives them wrong.
We gave the history back.
Gitmore exposes your repo's activity to the agent over MCP read-only, API key, no source code. Before it edits a file, the agent can ask what shipped this week, or search every PR description and commit message for why a thing changed.
Then the other direction, which matters more.
When a session ends, a Claude Code Stop hook posts a short self-report: what it did, why, the branch, the commit, the PR, the files it touched. Four thousand characters of reasoning that would otherwise have died with the session.
The next agent reads it. So does the next engineer.
Here's the part I underestimated. When one person used an agent occasionally, losing the "why" was an annoyance. When agents write a third of your merged work, losing the "why" is an institutional memory problem and it compounds quietly, commit by commit, until nobody can explain a subsystem.
Attribution tells you how much of your code agents wrote.
This decides whether any of that work accumulates into something your team actually knows.
gitmore.io
Top comments (0)