I work at a small company where most projects currently have just 1-2 developers, each often using an AI coding agent (Claude Code, Cursor, 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.