Can a crew of Claude Code sessions handle dependency upgrades in a documentation website?

Yes, Tares runs a crew of Claude Code sessions that can take dependency upgrades in a documentation website from plan to pull requests merged on main. You plan the upgrade as a project, and the orchestrator starts one builder per milestone and repo. Each builder opens pull requests that the reviewer checks and CI must pass before they merge.

How it works

The crew is an orchestrator, a reviewer and builders, all Claude Code sessions running in the background on your machine. Tares holds the plan, the tickets, the reviews and your answers, so a crew that restarts carries on where it stopped.

For a documentation site, the repo shapes the work in these ways:

• Builders per milestone and repo. The orchestrator starts one builder for each milestone and repo of the project, up to the number of builders you allow. If your docs site and a shared component library are two repos in one upgrade project, each milestone in each repo gets its own builder.
• One ticket, one branch, one pull request. A builder takes a ticket, works on its own branch and opens a pull request. Split an upgrade into tickets, such as one per group of packages, and each one becomes its own reviewable pull request.
• What a pull request has to pass. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request. The builder merges only after the reviewer passes it and CI is green. Tares reads the pull request, CI and merge state of every ticket itself.
• Acceptance checks in the plan. The planning step writes milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. That is where you pin down what done means for the upgrade.
• Language servers. tares factory doctor reads each handed-over repo’s languages from its manifests, for example package.json for JavaScript or tsconfig.json for TypeScript. It tells you whether Claude Code has a language server for each, so builders and the reviewer can search by symbol.

You talk to one session, the orchestrator. Questions from every project reach you there, one at a time, each with a recommendation.

Set it up

Follow these steps in order. The Get started page has the full walkthrough.

1. Check that Claude Code is signed in on a plan that allows background sessions. Sign in to gh with write access to the docs repo, and make sure git, jq and curl are installed.
2. Install the CLI and start Tares locally.
3. In a second terminal, start the MCP endpoint every crew session shares. On Tares Cloud, run tares login instead and skip this step.
4. Give Tares access to GitHub: add a token or App under Settings > GitHub for a local Tares, or choose Connect GitHub on Tares Cloud.
5. Bring up the crew. The first run asks how far the crew may go: merge on its own after review and green CI or wait for your yes, whether a second model checks every commit, and how many builders run at once.
6. From the docs repo, or a folder that holds its repos, plan the upgrade project.

gh auth login
uv tool install tares     # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

In the spec interview, describe the upgrade you want, such as which dependencies to move and what the docs build must still do. 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 follow progress on the Crew page at http://127.0.0.1:8787/crew.

tares factory crew attach orchestrator
tares factory doctor

What you get

• Upgrade work split into tickets, each landing as its own pull request on its own branch.
• Builders assigned per milestone and repo, so work across several repos runs side by side while the reviewer reviews every pull request.
• A fixed review bar and green CI before anything merges. You can also make a single project wait for your yes before every merge.
• A written record of every assumption the crew made and every answer you gave, so you can check the choices at the end of each milestone instead of during every step.
• Progress on the Crew page, plus tares factory projects for each project’s progress, builders and repos.

When something else fits

• For a small upgrade, work in your own Claude Code session with tares factory session, which still records the work on the project.
• The factory is built for solo developers and very small teams on one machine, using your own Claude Code login and GitHub repos. If you need something beyond that, a crew is not the fit today.

Related