Xerum for software teams
Your agent should know why the code is like that
The reasoning behind your system lives in closed issues, review threads and an incident doc somebody wrote at 2am. None of it reaches the model — so the model guesses, confidently, and somebody merges it.
Sound familiar?
The answer is in a closed thread
Somebody argued it out in a pull request eighteen months ago and was right. That thread is not in the repo, not in the docs, and not in any context window — so the same trade-off gets re-litigated every time a new person touches the file.
Your agent invents the rationale
Ask why a queue is there and you get a plausible paragraph about decoupling. It reads well. It is not what happened, it names no source, and there is nothing in the answer that would let you notice.
Docs describe the system that was planned
A wiki records the intention at the moment somebody had time to write it. The decisions that actually shaped the system arrived afterwards, in threads, and nobody went back to update the page.
What changes
The conversation layer, not the code
The GitHub connector reads issues, pull requests and their review threads, docs and releases — the places where the reasoning is, rather than the places where the result is.
Every claim clicks through
An answer carries the revision it was read at, the resource it came from and the origin URL. You land on the review comment where a human actually made the call.
Read the repo as of any revision
Diff two revisions to see exactly which change moved an answer, who wrote it and what their message said. Post-incident review stops being a memory exercise.
One context, every agent
Claude, Cursor, whatever the team standardises on next quarter — connect once over MCP and they all read the same thing, filtered to what each person may see.
What this industry buys
Provenance + time travel
The two properties a software team feels first — and the two that make an agent answer trustworthy enough to act on.
- Answers end at the URL where somebody wrote the reasoning
- Any question can be asked as of an older revision
- Audit is reading the changes; there is no separate audit log
- GitHub connector running today, Jira and Slack next
This is the wedge — the connector we built first, against the source we know best.
Related
Ask your agent why /search got slow last quarter
Built today, not on a roadmap. Every property above is already how the store works.