@rohanpaul_ai: Treating agent memory like a Git repo, with commits and branches, lets agents drop outdated requirements and keep the w…

X AI KOLs Timeline Papers

Summary

研究提出将智能体记忆类比 Git 仓库,通过 commits 与 branches 管理任务版本,使智能体能丢弃过期需求并从正确版本恢复。方法 GitHarness 在全部 30 个测试设置中优于普通续跑,某设置下编码任务 token 消耗减少 73.6% 且得分更高。

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.
Original Article
View Cached Full Text

Cached at: 10/05/26, 01:32 PM

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.

Similar Articles

@Xudong07452910: Agent memory is most dangerous when it trusts the past too much. Many Memory Agents stuff similar experiences directly into context after retrieval. But similar tasks do not mean the current state is the same; old experiences can sometimes steer decisions astray. This paper proposes MemHarness, turning Agent...

X AI KOLs Timeline

MemHarness proposes changing Agent memory from simple replay to reconstruction based on the current state, trained end-to-end with GRPO, significantly improving success rates on ALFWorld and WebShop.

@WY_mask: Build persistent memory engine for all kinds of AI coding assistants http://github.com/rohitg00/agentmemory… Silently records code changes and context in the background, automatically extracts and compresses into structured memory, saves Token consumption from long context, associates past information, as…

X AI KOLs Timeline

agentmemory is an open-source tool that provides persistent memory for AI coding assistants. It silently records code changes and context, automatically extracts and compresses them into structured memory, reduces Token consumption, and supports multiple mainstream platforms such as Claude Code and Codex.

@wsl8297: When running complex tasks with AI agents, the most painful thing is often not that the model isn't strong enough, but that as the conversation gets longer, the context starts to overflow. You have to keep filling in background details, re-explaining the process, plus the redundant logs from tool calls — tokens just gush out like a broken pipe. Recently, I saw TencentDB Agent Memory open-sourced by Tencent...

X AI KOLs Timeline

Tencent has open-sourced TencentDB Agent Memory, which solves the AI agent long-context overflow problem through hierarchical memory management (symbolic short-term memory + hierarchical long-term memory). Benchmarks show token consumption reduced by up to 61% and task success rate improved by over 50%.