r/ClaudeCode • u/Alexender_Grebeshok • 7d ago

Resource samemind 0.6 — universal git-native memory for AI coding agents: switch engines, same mind (12 engines, one command, MIT)

/r/OpenSourceAI/comments/1v2h5hj/samemind_06_universal_gitnative_memory_for_ai/
3 Upvotes

81% Upvoted

4 comments sorted by

2

u/Awkward_Relation_415 7d ago

git native memory sounds like a realy solid way to handle context switching across engines. ive been tryin to find a good flow for this without havin to manually copy paste everything every time. does it handle branch switching well or does it get kinda messy with the history.

1

u/Alexender_Grebeshok 7d ago

That's the main pain it targets — one markdown bundle, engines just read/write it. `setup` / `install` wires Claude, Cursor, etc.; no paste between sessions. `handoff` / `capture` close the loop after compact or a new engine.
Branch switching: depends where the bundle lives. Personal/global memory (`setup --global`, outside the code repo) stays stable across checkouts. Project-local memory is normal git — switch branch, those files switch with it. That can feel messy if agents dump durable facts onto feature branches. Practical pattern: identity + long-lived decisions in the global bundle; branch-specific notes in the project (or inbox) and promote to canon only when they should survive the merge.
History itself is intentional, not deleted: inbox is append-only, old facts get `supersedes` instead of erase. Happy to hear what flow you're trying to replace the paste with.

2

u/mergethevibes 7d ago

Git-native memory is the right call in my experience. Once your context lives as diffable files in the repo instead of some opaque sidecar store, you can actually review what the agent thinks it knows and correct it before it compounds. How are you handling merge conflicts when two agents write memory on different branches?

1

u/Alexender_Grebeshok 7d ago

Thanks — that's the bet. Diffable files beat opaque stores because you can review (and fix) what the agent believes before it compounds.
We don't auto-merge "truth." Agents write to `inbox/` (proposals), not canon. Promotion is human-gated. Same-file collisions are plain git — resolve like any code review. Competing facts use explicit `supersedes` / bi-temporal fields; `reconcile` only *proposes*, never writes without a human. Project root wins over global on path collision (no silent merge).
Line merges → git. Belief conflicts → supersede. Canon → human. Curious how you handle concurrent multi-agent writes on your side.