Keep the Why vs. past.dev vs. Agent Memory Repo vs. agentmemory
Four tools called agent memory. Four different approaches to what should survive. One puts decision rationale next to the code.
#git
Posts tagged #git
Keep the Why vs. OKF Agent Memory vs. RepoWise: Three Approaches to Git-Native Project Memory
Rationale, structured knowledge, or codebase intelligence for coding agents?
The Globe: Following Your Reasoning Into Other People's Repositories
Keep the Why records why a codebase is the way it is. Decisions can cite decisions in other repositories. The Globe follows those citations outward, one wave at a time, without turning project memory into a centralized service.
The reasoning behind a codebase, as a web you can walk
Decisions that cite each other across repositories — no graph database, no central index, no account. Just Markdown and Git.
Your repository already is your project's memory. One layer was missing.
Project memory is not another database for your coding agent. AI exposed the one thing the repository was systematically missing: why.
One Index, Many Writers: Avoiding Git Merge Conflicts with Deterministic Write Areas
How a small structural change reduced unnecessary Git conflicts in a shared Markdown index — and made it easier for coding agents to navigate.
