An agent-native VCS still stores history the way teams expect — commits, branches, protection rules — but exposes a query plane optimized for tools: structural search, symbol resolution, change impact, provenance, and packaging of only the slices an agent needs for the current task. Throughput Lines of Code Per Day sits on that boundary: warm forge for canonical truth, phosphor for derived intelligence. AI proposes; humans merge; the graph rebuilds from truth.
Blogengineering1 min read
Agent-Native VCS Architecture
Version control was built for humans reviewing diffs. Agents need a different primary interface.
Chat-first coding agents inherited git as a storage layer and a text dump as a context strategy.
Build agents that query the repo like a system of record, not a bag of files.
Continue
Welcome to Throughput Lines of Code Per Day
Agent-native version control that query-maps your repository instead of dumping files into context.
10.7x Context-Token Savings: How We Measured It
Every number on our benchmarks page is copied from measured runs — not marketing fiction.
Why Sidecar Code Graphs Go Stale
Sidecars proved agents need a graph. They also proved a second source of truth is a liability.