GitHarness: agent memory as a Git repo cuts tokens 73.6% in one coding setup
rohanpaul_ai · x · 2026-10-05
GitHarness treats an agent's memory like a Git repo: each requirement is stored with its matching work like a commit, and when a user changes requirements mid-task, the agent branches from the closest still-valid version and redoes only what actually changed.
The root problem: users rarely give a full spec upfront — they add, fix, or drop requirements as results come in, and most agents either carry stale work forward or redo everything.
- GitHarness beat plain continuation in all 30 tested settings.
- In one coding-task setup it used 73.6% fewer tokens while scoring higher.
Takeaway: any agent that takes user feedback should build versioning into its memory.
Related event: GitHarness Manages Agent Memory Like Git, Cutting Tokens 73.6%(3 posts)→
More from coding & agent
- TanStack AI adds experimental text-to-GLB 3D model and prompt-to-motion animation generation — bennash · 2026-11-20
- Dev builds typing survival game with troops and skill trees in ~24 hours using agents and kaigen3d — hullabaloo22 · 2026-11-20
- Harmonic's Aristotle writes proven-correct fusion plasma controllers in C and Verilog in 4 hours — satnam6502 · 2026-11-20
- R3 Code: A Native Rust Mac Client That Runs All Your Coding Agents — jasonkneen · 2026-11-20
- zlib: 2.4K-star open-source CLI turns Z-Library into a skill for AI agents — udmrzn · 2026-11-20
- Andriy Burkov's True Positive Weekly #186: what to know when agents do the work — burkov · 2026-11-20