Can a crew of Claude Code sessions handle docs updates in a monorepo?

Yes, Tares runs a crew of Claude Code sessions that can take docs updates in a monorepo through to pull requests merged on main. You plan the work as a project, the orchestrator starts builders per milestone and repo, and a pull request merges only after the reviewer passes it and CI is green. The steps are in Get started.

How it works

A docs update is handled like any other project. The crew is an orchestrator, a reviewer and builders, all Claude Code sessions on your machine. Tares keeps the plan, tickets, reviews and your answers, so a crew that restarts carries on where it stopped.

What the repo changes is how builders are assigned:

• Builders are per milestone and repo. The orchestrator starts one builder for each milestone and repo of a project, up to the number of builders you allow. A monorepo is one repo, so the split inside it comes from your milestones.
• Each builder works one ticket on its own branch. It opens a pull request and merges it once the reviewer passes it and CI is green.
• The crew serves many projects at once. A docs project can run next to code projects while the reviewer reviews every pull request.

What a pull request has to pass:

• The reviewer’s fixed bar. The reviewer reviews every pull request and posts its verdict on it.
• Green CI. Tares reads the pull request, CI and merge state of every ticket itself, so it needs its own GitHub access to the repo.
• The milestone’s acceptance checks. spec writes them into the plan for each milestone.
• An optional second model. You can have the Codex CLI check every commit.
• An optional wait for your yes. A single project can wait for you before every merge, even when the rest of the crew merges on its own.

Set it up

1. Check the prerequisites. Claude Code must be signed in, on a plan that allows background sessions. gh must be signed in with write access to the monorepo, and git, jq and curl must be installed.

   gh auth login

2. Install the CLI.

   uv tool install tares     # or: brew install glassflow/tap/tares

3. Point the crew at Tares. On a local Tares, start it, then start the MCP endpoint every crew session shares in a second terminal:

   tares up
   tares mcp --transport streamable-http

   On Tares Cloud, sign in instead and pick your workspace in the browser. There is no MCP endpoint to start.

   tares login

4. Give Tares access to GitHub, so it can read each pull request and its CI. On a local Tares, add a token or App under Settings > GitHub. On Tares Cloud, choose Connect GitHub and pick the monorepo.

5. Bring up the crew. The first run asks whether the crew merges on its own after review and green CI or waits for your yes, whether it releases, whether a second model checks every commit, and how many builders run at once.

   tares factory crew up

6. Plan the docs update from inside the monorepo, or from a folder that holds its repos. Ask for it in your own words, and say how you want it split into milestones.

   tares factory spec "what you want to build"

   The interview ends by asking whether to hand the project to the crew. Say yes and the orchestrator picks it up.

7. Answer questions in the orchestrator’s session, and check the setup at any point.

   tares factory crew attach orchestrator
   tares factory doctor

   tares factory doctor also reads the languages of each handed-over repo from its manifests, at the repo root or one folder down. It tells you whether Claude Code has a language server for each, and what to run for a missing one. tares factory projects lists each project’s progress, builders and repos.

What you get

• Docs updates that arrive as pull requests, one ticket per branch, and land on main once the reviewer and CI agree.
• Builders matched to your plan, one per milestone and repo, with the number running at once capped by the limit you set.
• A record on Tares of the plan, every review, the assumptions the crew made and your answers, so you can check its choices at the end of each milestone instead of during every step.
• One place to talk to the crew. The orchestrator is the only session you talk to, and the Crew page in the Tares console shows each project’s builders and the pull requests waiting for review.
• The option to hold one project for your approval before every merge.

When something else fits

• If the work is small, tares factory session lets you plan and build it in your own Claude Code session, still on Tares, without bringing up the crew.
• The software factory is built for solo developers and very small teams. It runs on one machine, on your own Claude Code login, against your own GitHub repos.

Related