mlsanityData to 14 Oct 2026

GitOfThoughts: Version-Controlled Reasoning and Agent Memory You Can Replay, Diff, and Merge

arXiv 2606.14470 ↗First posted 12 Jun 2026cs.AI cs.CL cs.LGcited by 1

On the map: LLM reasoning → Reasoning for agents, planning and code

also in 1 more
Abstract (arXiv)

Large language model reasoning leaves no trace once it is done. The steps of a chain of thought disappear when the context window closes, a pruned search branch is just gone, and memory buffers cannot be diffed, merged, or audited. Code, infrastructure, and experiments are all version-controlled. Reasoning is not. GitOfThoughts stores an agent's reasoning tree as a git repository. Every scored thought becomes a commit, scores become notes, outcomes become tags, and retrieval is just git log over the agent's own history. We use this to test something simple. Does giving an agent memory from past problems actually make it more accurate? We tried five memory stores (none, a markdown file, a vector database, a graph, and git) across two benchmarks, two model sizes, and several pre-registered repeat experiments. The answer, on new problems, is no, including one promising early result that did not hold up when we repeated it. Memory only helps once the problem being solved is nearly identical to something already in memory (cosine similarity above about 0.8); below that, it does nothing. In other words, the model is finding the answer rather than learning the method. Even a model 4.5x larger still cannot pull a reusable method out of a worked example; it just gets better at spotting near-copies. The only thing that reliably helped on new problems was generating several answers and picking the most common one (self-consistency). So the case for using git as the memory store is not that it retrieves better. It is that it gives auditability, history, and the ability to merge two agents' memories, at no cost to accuracy.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). Placed in Reasoning for agents, planning and code, one of 17 directions in LLM reasoning. Builds on 11 of its 30 references that are in the map. First posted on arXiv 12 Jun 2026.

Builds on

11 of 30 references.

References · 11

  1. 2024Qwen2.5 Technical Reportcited by 4,942
  2. 2023GPQA: A Graduate-Level Google-Proof Q&A Benchmarkcited by 2,879
  3. 2023Voyager: An Open-Ended Embodied Agent with Large Language Modelscited by 2,191
  4. 2024Scaling LLM Test-Time Compute Optimally can be More Effective than Scaling Model Parameterscited by 1,986
  5. 2023Improving Factuality and Reasoning in Language Models through Multiagent Debatecited by 1,784
  6. 2023MemGPT: Towards LLMs as Operating Systemscited by 1,389
  7. 2025A-MEM: Agentic Memory for LLM Agentscited by 1,063
  8. 2025Mem0: Building Production-Ready AI Agents with Scalable Long-Term Memorycited by 779
  9. 2024TextGrad: Automatic "Differentiation" via Textcited by 273
  10. 2023CLIN: A Continually Learning Language Agent for Rapid Task Adaptation and Generalizationcited by 95
  11. 2026ReTreVal: Reasoning Tree with Validation and Cross-Problem Memory for Large Language Modelscited by 1

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2026: 1.

1 paper.

Similar, not cited

Close in wording, no citation either way

  1. 2026Why Git Is the Memory Solution for the Agentic Development Lifecycle
  2. 2025Git Context Controller: Manage the Context of LLM-based Agents like Git
  3. 2026Git4Data: Database-Native Version Control for AI Agents
  4. 2026Weighted Memory Tree: Remembering What Matters for Long-Horizon LLM Agents
  5. 2026Git-Assistant: Planning-Based Support for Updating Git Repositories
  6. 2026CommitDistill: A Lightweight Knowledge-Centric Memory Layer for Software Repositories
  7. 2026Many Steps into One: Reasoning Contraction and the Limits of Safe Memory Reuse for LLM Agents
  8. 2026Lore: Repurposing Git Commit Messages as a Structured Knowledge Protocol for AI Coding Agents