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
- Dev ships AI-built game by looping relentless AI critique, using Three.js, ElevenLabs and Suno — AIandDesign · 2026-10-05
- Karpathy shares tips for reading LLM outputs: ASD-STE100 writing and diagrams — dair_ai · 2026-10-05
- Dev rebuilt his coding agents' UI as iMessage and says life is better now — davidfromkansas · 2026-10-05
- Redditor builds offline AI agent network across Legion laptop and iPhone with Tailscale — Due_Recording_5802 · 2026-10-05
- Every MCP tool passed in isolation, yet the workflow still failed — test full chains — Stock-Pumpkin-8859 · 2026-10-05
- Instead of booking flights, these are the agent demo tasks people actually want — vivekhaldar · 2026-10-05