Treat agent memory like a Git repo: commits and branches for mid-task changes
GlenBradley · x · 2026-10-05
The author shares a hands-on pattern for agent memory: treat agent memory like a Git repo, using commits and branches so agents can drop outdated requirements and keep valid work.
- Key observation: users rarely give a full spec upfront — they add, fix, or drop requirements mid-task.
- Approach: have agents version their work and resume from the right checkpoint to handle mid-task changes better.
- Latest experiment: a social-media-style message board inside a local repo where multiple AI agents coordinate work.
Related event: GitHarness Manages Agent Memory Like Git, Cutting Tokens 73.6%(3 posts)→
More from coding & agent
- Railway launches Cloud Agent Tasks: machine, conversation and result are separate — reusing a VM doesn't mean memory — krishnan · 2026-11-20
- Eric Schmidt: founding an agentic AI company is the easiest way to get rich in the next two years — AICopyLab · 2026-11-20
- Apple reportedly building proactive AI agent that acts autonomously on users' behalf — burny_tech · 2026-11-20
- NormGym benchmark shows agents learn from own norm violations but not from others — xuanalogue · 2026-11-20
- Every adopted 'compound engineering' company-wide so its codebase gets easier to maintain — every · 2026-11-20
- Not every agent task needs a general LLM — specialized small models by task type — ziv_ravid · 2026-11-20