Can a crew of Claude Code sessions handle bug fixes in a Node/TypeScript app?

Yes, Tares runs a crew of Claude Code sessions that turns bug fixes in a Node/TypeScript app into pull requests merged on main. You describe the fixes, the orchestrator starts one builder per milestone and repo, and the reviewer and CI hold every pull request to the bar before it merges. The crew works with your own Claude Code login and your own GitHub repos.

How it works

The crew is a set of 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 your app, the repo shapes the work in three ways:

• Builders are assigned 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. If your bug fixes touch one Node/TypeScript repo, each milestone gets one builder on that repo. If they span an API repo and a frontend repo, each repo gets its own builder.
• Each builder takes a ticket and works on its own branch. It opens a pull request for that ticket. Builders push and open pull requests with your gh login.
• Every pull request has to pass two gates. The reviewer reviews it to a fixed bar and posts its verdict on the pull request. CI on the pull request has to be green. A builder merges only after both pass.

The plan sets the checks a milestone has to meet. /tares:spec writes milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. Tares reads the pull request, CI and merge state of every ticket itself, so the ticket list shows where each fix stands.

You can also make one project wait for your yes before every merge, even when the rest of the crew merges on its own.

Set it up

1. Check that Claude Code is signed in on a plan that allows background sessions, that gh is signed in with write access to your app’s repo, and that git, jq and curl are installed.

2. Install the CLI and start Tares and the shared MCP endpoint. Leave both running.

   uv tool install tares     # or: brew install glassflow/tap/tares
   tares up                  # console on http://127.0.0.1:8787
   tares mcp --transport streamable-http     # http://127.0.0.1:8788/mcp

3. In a third terminal, run tares login if you use Tares Cloud, and give Tares access to your GitHub repos so it can read pull request, CI and merge state. On Tares Cloud, use Connect GitHub in your workspace settings. On a local Tares, add a GitHub token or App under Settings > GitHub.

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

5. From inside your Node/TypeScript repo, plan the bug fixes. The interview asks one question at a time, writes the milestones and tickets, and ends by asking whether to hand the project to the crew. Say yes.

   tares factory spec "fix the checkout and login bugs in this app"

6. Answer the crew’s questions in the orchestrator’s session.

   tares factory crew attach orchestrator

7. Run tares factory doctor at any point to check everything the crew needs. For the full walkthrough, see Get started.

What you get

• Each bug fix becomes a ticket, a branch and a pull request, built by a builder assigned to that milestone and repo.
• Every pull request carries the reviewer’s verdict and runs against your repo’s CI, and nothing merges until both pass.
• Tickets can live in Tares, in a Linear project or in GitHub Issues. If your team already tracks bugs in Linear or GitHub Issues, sessions change them there and Tares reads them about once a minute. Tares never writes to them.
• The Crew page in the Tares console shows each project’s progress, its builders and the pull requests waiting for review.
• Questions from every project reach you in one place, the orchestrator, one at a time with a recommendation. Choices the crew made on its own are written down, so you can check them at the end of each milestone.
• One crew serves many projects at once. While one project waits for you, the others carry on.
• Use tares factory projects to see each project’s progress, builders and repos, and tares factory crew status for the stations and the questions waiting for you.

When something else fits

• For one small bug, work in your own Claude Code session still on Tares with tares factory session "<idea>". It plans a small project and builds it right there, and it offers the full spec and crew hand-over if the plan turns out big.
• 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