Skip to Content
Tares

Can a crew of Claude Code sessions handle test coverage in a Node/TypeScript app?

Yes, Tares runs a crew of Claude Code sessions that can take a test coverage project in a Node/TypeScript app from plan to merged pull requests. The orchestrator starts one builder per milestone and repo, and each pull request merges only after the reviewer passes it and CI is green. You plan the work once, answer the few questions the crew asks, and check the result on main.

How it works

The crew is a set of Claude Code sessions running in the background on your machine, and Tares keeps the plan, tickets, reviews and your answers.

  • Planning. You describe the test coverage work and /tares:spec turns it into a Tares project: a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md. The acceptance checks are where you say what done means for your Node/TypeScript app.
  • Builders per milestone and repo. The orchestrator starts one builder for each milestone and repo of the project, up to the number you allow. A Node/TypeScript app in one repo gets one builder per milestone. If the app spans several repos, each repo gets its own builder for that milestone.
  • One ticket at a time. Each builder takes a ticket, works on its own branch and opens a pull request.
  • The gates. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request. The builder merges once the reviewer passes it and CI is green. Nothing merges before that.
  • Language servers. Builders and the reviewer search less when Claude Code can find definitions, references and callers through a language server. tares factory doctor reads your repo’s manifests: a tsconfig.json marks TypeScript and a package.json marks JavaScript. It then says whether Claude Code has a server for each and prints what to run for a missing one.

If the crew restarts, it carries on where it stopped, because the record stays on Tares.

Set it up

  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
  1. Install the CLI.
uv tool install tares     # or: brew install glassflow/tap/tares
  1. On a local Tares, start it with tares up. In a second terminal, start the MCP endpoint every crew session shares with tares mcp --transport streamable-http. On Tares Cloud, run tares login and pick your workspace in the browser instead.
  2. Give Tares access to GitHub, so it can read the pull request, CI and merge state of every ticket. On a local Tares add a token or App under Settings > GitHub. On Tares Cloud choose Connect GitHub. The Get started page covers both.
  3. Bring up the crew. The first run asks how far the crew may go: whether it merges on its own after review and green CI or waits for your yes, whether it releases, and how many builders run at once. If your Node/TypeScript repo has no language server wired in for Claude Code, crew up lists what is missing and installs only when you say yes.
tares factory crew up
  1. In the repo, or a folder that holds its repos, plan the project. Describe the test coverage work you want, such as the modules to cover and what counts as done.
tares factory spec "what you want to build"
  1. Say yes when it asks whether to hand the project to the crew, then answer questions in the orchestrator’s session.
tares factory crew attach orchestrator
  1. Run tares factory doctor at any point to check everything the crew needs, including the language servers for your repo.

What you get

  • Pull requests for each ticket of your test coverage project, built on separate branches and merged on main once the reviewer passes them and CI is green.
  • A review verdict on every pull request, held to the same fixed bar for every change.
  • Builders split by milestone and repo, so a multi-repo Node/TypeScript setup gets separate builders for each repo.
  • The option to make one project wait for your yes before every merge, while the rest of the crew merges on its own.
  • A written record of the assumptions the crew made on its own, so you can check them at the end of each milestone instead of during every step.
  • The Crew page in the Tares console, which shows each project’s progress, its builders and the pull requests waiting for review.
  • Several projects at once. The crew works on all of them, and while one waits for you, the others carry on.

When something else fits

  • For a small coverage task, work in your own Claude Code session with tares factory session. It plans a small project and builds it there, with your shared AGENTS.md and memory applied and the record landing on the project.
  • The crew fits solo developers and very small teams who already use Claude Code, because it runs on one machine, on your own Claude Code login, against your own GitHub repos.

Still stuck? Get help

Last updated on
Quickstart