Monorepos#

Your work spans several repositories: a public library, its docs site, and a private service. One change touches two or three of them. You clone each one by hand, and your agent must be told about each one.

A monorepo on TanStack Source is a repository with members. Each member stays its own repository, with its own history and its own access. The monorepo puts them side by side: one checkout, one search, one pull request across members, and one context for your agent. Nothing is copied between repositories.

Pick your task#

• Make a monorepo: add member repositories to a repository of your organization.
• Who can see a monorepo: mix public and private members, and keep the private ones private.
• Clone and sync a monorepo: get every member in its own folder with one command.
• Give an agent a monorepo: one session, one token and one agents.md for all members, and factory agents that work across members.
• Change several members in one pull request: open one monorepo pull request, review its parts, and merge them all with one action.
• Test a change across members in CI: build each part with the other members next to it, and run the monorepo's own checks.

How a checkout looks#

platform/            the monorepo's own clone (root files, such as AGENTS.md)
platform/web/        a normal clone of acme/web
platform/docs/       a normal clone of acme/docs
platform/billing/    a normal clone of acme/billing

Each folder is a normal git clone, with its own .git. Nothing in a member names the monorepo.