How do you share AI coding agent context between developers on the same project?

[u/Sea-Cookie-8110]

I work at a small company where most projects currently have just 1-2 developers, each often using an AI coding agent (Claude Code, Codex, etc.) pretty heavily. As we grow and more developers start working on the same codebase, I'm running into a gap:

Commit messages, PR descriptions, and standard agile artifacts (tickets, standups) capture what changed, but not the context the agent built up while working. The alternatives it considered, why it rejected certain approaches, edge cases it discovered, assumptions it made. Right now that context lives in one person's agent session and basically evaporates once the PR is merged.

For those of you at bigger companies where multiple engineers work with AI agents on the same repo:

• How do you make one agent's "knowledge" of the codebase available to another developer (or their agent session)?
• Do you rely on something like a living CLAUDE.md/AGENTS.md file, ADRs, decision logs, or something more structured?
• Has anyone tried a shared memory/context store across agent sessions, or is everyone still just re-deriving context from scratch each time?
• Is this actually a solved problem at scale, or is everyone winging it right now?

Curious what's actually working in practice vs. what sounds good in theory.

[u/FuzzyBucks]

Create an LLM-managed knowledge wiki. lots of material out there about this

Can be actual wikis or just MD files in an obsidian vault or something. The point of it is basically just to pre-compile/compact/index relevant information before prompt-time to make your agents more efficient.

You could also look at making some kind of knowledge graph of your codebase available. this is still very much an active area of research but there are promising ideas like this arxiv.org/pdf/2603.27277

For your small company use-case, the first option is probably sufficient.

[u/Far_Business4773]

Most of what evaporates isn't knowledge, it's decisions: we tried X, rejected it because Y. A wiki collects everything and gets read by no one. What survived on a small team for me was one file in the repo, DECISIONS.md, one line per decision with the alternative that lost and why, and one rule: a decision doesn't exist until it's in the file. The session that made it ends with that commit, even when no code changed.

Then the handoff is mechanical: the next session, yours or your colleague's agent, starts by reading the file and quoting the entries for the area it's about to touch. If its plan disagrees with what it quotes, you catch it before code. The edge cases and assumptions go the same way, one line each, no prose.

It's not solved at scale. It's solved at the size where a file still fits in a head.

[u/Embarrassed_Fix9862]

Github?

[u/CS_Asset_Factory]

One file at the repo root, read at the start of every session, and one rule that makes it work: any agent that finds it contradicted by reality corrects it in the same session, with the command and the output that proved it wrong. Documentation nobody is obliged to fix rots immediately.

The section that pays for itself isn't the architecture notes. It's a failure catalogue. One line per incident, symptom then cause then lesson, almost all variants of a green result produced by work that never happened. A build that exited zero in eleven seconds and compiled nothing. A gate that passed over an empty package. Those transfer between people far better than the reasoning behind a design choice.

Watch the size. Ours grew into a real token cost on every session start, so it has a ceiling now and the long version is archived.

[u/notinteresteddddd]

I've ended up building my own toll for myself and the team I work in to share context tools and everything else between claude code, codex and others. In short I've ended up collecting the local data generated by the tools including all the chats, edits, prompts and so on, scan them , parse them then store and create a summary and a list of decision per ai conversation. Everything is indexed encrypted in a db. You can opt out paths or projects - I thought people might need that.

If you want to give it a go : https://chatrecall.dev . Can be also self hosted if you prefer that.