1d ago
Version Control for the Age of Agents
We need a dual-layer, rich metadata, version control system that gives agents reproducibility and gives humans legibility. Every commit has two faces: one the machine can replay, one the human can understand. It ships as an API, a CLI, and a native integration inside Claude Code.
Problems 1.The Lost Prompt 2.The Unreviewed Mountain (of commits) 3.The Regression Nobody Caught
This is how we can build this: āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā HUMAN LAYER ā ā ā ā What developers see: ā ā ⢠Narrative commit messages (auto-generated) ā ā ⢠Intent diffs ("what was the agent trying to do") ā ā ⢠Risk scores per commit ā ā ⢠Architecture impact summaries ā ā ⢠Standard git clone / push / pull ā ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā⤠ā AGENT LAYER ā ā ā ā What the system records: ā ā ⢠Full prompt + system prompt at time of execution ā ā ⢠Model ID + version + hyperparameters ā ā ⢠Tool calls (terminal, browser, file reads) ā ā ⢠Reasoning traces (where available) ā ā ⢠Token usage + cost ā ā ⢠Session graph (which tasks spawned which) ā ā ⢠Eval results (per-commit and per-session) ā ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā