Git as a shared context layer for multi-agent teams: diffs beat prompts, but semantic conflicts slip through

and_pf · reddit · 2026-09-17

A thorough breakdown of using Git as a shared context layer for team agents:

Two naive approaches fail: stuffing everything into one growing prompt goes stale and is expensive to re-read; a shared database backend becomes an unauditable black box
Git's real value: every commit is a reviewable diff, every branch a scoped state slice, conflicts visible — exactly what multi-agent coordination needs
The unstated caveat: Git's merge is line-based; two agents asserting the same key with different values in a prose file triggers no conflict. You need a schema with a validation gate or a custom merge driver, or meaning silently diverges
Write discipline matters more than storage: gate writes with a propose-and-confirm flow, or human review becomes the bottleneck
Storing isn't remembering: citing the Lyzr Cognis paper (arXiv 2604.19771), retrieval pipelines (pull existing memories → extract → index → retrieve) must be built on top; Git doesn't search your decisions
Ends by asking what people use for retrieval when shared state lives in Git instead of a vector DB

More from coding & agent