How does the crew’s work on framework migrations reach main?

Tares moves the crew’s work to main through pull requests. A builder takes a ticket, works on its own branch and opens a pull request. The reviewer posts its verdict on that pull request, and the builder merges once the reviewer passes it and CI is green. Tickets end at merged on main unless you also ask for a releaser.

How it works

The software factory for Claude Code is a crew of Claude Code sessions running in the background on your machine. Tares holds the plan, the tickets and their stages, and every review. Each ticket moves to main like this:

• A builder takes the ticket. The orchestrator starts one builder per milestone and repo of a project. The builder works on its own branch.
• The builder opens a pull request. It pushes and opens the pull request with your gh login.
• The reviewer posts a verdict. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request.
• The builder merges. When the reviewer passes the pull request and CI is green, the builder merges it.
• The ticket ends at merged on main. A releaser, which tags and deploys, exists only if you ask for one.

Tares reads the pull request, CI and merge state of every ticket itself, so the ticket list and the Crew page stay current without anyone updating them by hand. The sessions can restart, and the record of plans, reviews and your answers stays on Tares, so a restarted crew carries on where it stopped.

You choose how much freedom the crew has when you first run tares factory crew up. It asks whether the crew merges on its own after review and green CI (the recommended setting) or waits for your yes. A single project can also wait for your yes before every merge while the rest of the crew merges on its own.

Set it up

Follow these steps in order. Steps marked local apply to a local Tares, and the step marked cloud applies to Tares Cloud. Full details are on Get started.

1. Check that Claude Code is signed in on a plan that allows background sessions. Sign in to gh with write access to the repos the crew works in, and make sure git, jq and curl are installed.

   gh auth login

2. Install the CLI.

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

3. Local: start Tares.

   tares up

4. Local: in a second terminal, start the MCP endpoint every crew session shares. The crew reaches a local Tares only through this endpoint, so start it before the crew.

   tares mcp --transport streamable-http

5. Cloud: sign in and pick your workspace in the browser.

   tares login

6. Give Tares access to the repos so it can read pull request, CI and merge state. On a local Tares, add a GitHub token or App under Settings > GitHub. On Tares Cloud, choose Connect GitHub.

7. 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.

   tares factory crew up

8. Plan the project. The plan becomes milestones and tickets that the orchestrator hands to builders.

   tares factory spec "what you want to build"

9. Follow the pull requests on the Crew page of the Tares console, or from the terminal.

   tares factory crew status
   tares factory projects

Run tares factory doctor at any point to check everything the crew needs.

What you get

• Work that reaches main as a pull request from a builder’s own branch, with the reviewer’s verdict posted on it.
• A merge only after the reviewer passes the pull request and CI is green.
• One reviewer holding every pull request to the same fixed bar.
• A Crew page that lists each project’s builders and the pull requests waiting for review.
• A record on Tares of the plan, tickets, reviews, assumptions and your answers, so you can check the crew’s choices at the end of each milestone instead of during every step.
• Control over merging. You can have the crew merge on its own or wait for your yes, per project if you like. tares factory crew halt stops merges, pushes and new sessions until tares factory crew resume.

When something else fits

• If one change is small enough to do yourself, run tares factory session to work on a project in your own Claude Code session, still on Tares. If the crew already has the project, the session asks whether to take it over, and the crew stops only if you say yes.
• If you want a person to approve every merge, set the crew or a single project to wait for your yes.

Related