We have a large enterprise system with dozens of frontend apps, backend services, and integration projects spread across many repositories. A common problem is that when Claude Code works on a single repository, it lacks context from the rest of the system: Which service owns a capability? What other repositories are involved in a workflow? What systems would be impacted by a change? Where should a new feature actually be implemented? My initial idea was to create an Agent for each repository, plus a Lead Agent that coordinates tasks and gathers information from other Agents when needed. After discussing it with AI, it suggested a different approach: building a centralized knowledge base (architecture, project relationships, APIs, business flows, domain models, etc.) and exposing it through MCP/RAG, with AI retrieving information on demand instead of relying on multiple Agents. Has anyone here dealt with this problem at scale? Which approach worked better in practice: Multi-Agent (one Agent per repo + Lead Agent) Centralized knowledge base / MCP / RAG A hybrid approach Something else entirely I’d love to hear real-world experiences and lessons learned. submitted by /u/KennenHou
Originally posted by u/KennenHou on r/ClaudeCode