Article · Original
Treating agent memory like a Git repo, with commits and branches, lets agents drop outdated requirements and keep the work that is still valid.
Agents handle mid-task changes from users better when they save versions of their work and resume from the right one, so build that versioning into any agent that takes feedback.
Users rarely give a full spec upfront. They add, fix, or drop requirements as results come in. Most agents then carry stale work forward or redo everything.
GitHarness stores each requirement with its matching work, like Git commits, and branches from the closest valid version. It beat plain continuation in all 30 tested settings. In 1 setup, it used 73.6% fewer tokens on coding tasks while scoring higher.
When a user changes 1 detail, go back to the version that still fits and redo only what changed.