Monorepo

concept · updated Jun 10, 2026

person concept tool org talk claim — click a node to jump to its page; hover an arrow for the relation

A monorepo is a single version-controlled repository containing multiple packages or projects, organized to share tooling and dependencies while maintaining internal separation by domain or architectural layer.

Structure and scale at OpenAI

Ryan Lopopolo describes OpenAI's frontend codebase as a PNPM workspace monorepo containing 750 packages, isolated by business logic domain or layer of the stack. 57:20

Relevance to agent-based engineering

The claim surfaced in the context of how repository structure affects AI agent performance. The argument is that structuring a repository into many small, isolated packages improves agent outcomes by:

  • Creating transferable context: consistent patterns across packages allow agents to apply learned conventions broadly.
  • Scoping changes to directory subtrees: agents work within bounded, well-defined boundaries rather than navigating an undifferentiated codebase. 57:20

This positions the monorepo—when decomposed finely enough—as a form of implicit scaffolding that constrains and guides agent behavior without requiring explicit instruction at runtime.

Points of disagreement

No competing perspectives on monorepos appear in the current graph material. The sole account is Lopopolo's advocacy for fine-grained package decomposition within a PNPM workspace as a best practice for human-agent collaborative engineering.