Can a crew of Claude Code sessions handle small features in a Node/TypeScript app?

Yes, Tares runs a crew of Claude Code sessions that takes small features in a Node/TypeScript app from plan to merged pull requests on main. You describe the feature with tares factory spec, and the orchestrator starts one builder per milestone and repo of the project. Each builder opens a pull request that merges once the reviewer passes it and CI is green.

How it works

The crew is an orchestrator, a reviewer and builders, all Claude Code sessions running in the background on your machine. A releaser joins only if you ask for one. For a Node/TypeScript app, the repo shapes the work in three ways.

• Builders follow milestones and repos. When you plan a feature, Tares writes a project with a spec, milestones with acceptance checks, and tickets with a working doc each. The orchestrator starts one builder per milestone and repo, up to the number you allow. A small feature in a single repo with one milestone gets one builder. A feature that spans an API repo and a web repo gets a builder for each repo.
• Each builder works alone on a ticket. A builder takes a ticket, works on its own branch, opens a pull request, and merges it once the gate below is met.
• Two checks gate every merge. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request. CI must be green. Tares reads the pull request, CI and merge state of every ticket itself, so it needs its own GitHub access to the repo. Nothing merges until both checks pass.

The plan, tickets, reviews and your answers stay on Tares. If a session restarts, the crew carries on where it stopped.

If Claude Code finds package.json or tsconfig.json in a handed-over repo, tares factory doctor checks whether a TypeScript or JavaScript language server is set up. Builders and the reviewer search less when Claude Code can follow a definition, its references and its callers. When a server is missing, doctor prints what to run, and tares factory crew up offers the same install and runs it only when you say yes.

Set it up

1. Check that Claude Code is signed in on a plan that allows background sessions, and that gh is signed in with write access to your app’s repo. Also install git, jq and curl.
2. Install the CLI and start Tares. On a local Tares, start the MCP endpoint in a second terminal, because every crew session reaches Tares only through it. On Tares Cloud, run tares login instead and skip tares up and the MCP step.
3. Give Tares access to GitHub. On Tares Cloud, choose Connect GitHub in your workspace settings and pick the repo. On a local Tares, add a GitHub token or App under Settings > GitHub. The GitHub page has both paths.
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, and how many builders run at once.
5. In your app’s repo, plan the feature. Claude Code interviews you one question at a time and writes the project, milestones and tickets.
6. Answer the orchestrator’s questions in its session. Run tares factory doctor at any point to check the setup.

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 "add a CSV export button to the reports page"
tares factory crew attach orchestrator
tares factory doctor

The Get started page covers each step in more detail.

What you get

• Small features become pull requests merged on main, with each pull request reviewed to a fixed bar.
• Work is split by milestone and repo, so a feature across several repos gets several builders at once, up to the limit you set.
• You talk to one session, the orchestrator, and your time goes to the plan and the few questions the crew cannot answer itself.
• The Crew page of the Tares console shows each project’s progress, its builders, and the pull requests waiting for review.
• Every choice the crew made on its own is written down, so you can check it at the end of each milestone.
• You can set one project to wait for your yes before every merge while the rest of the crew merges on its own.

When something else fits

• For a very small change you want to drive yourself, run tares factory session and build it in your own Claude Code session. It stays bound to the Tares project, so your shared AGENTS.md and memory apply.
• The software factory is built for solo developers and very small teams working in their own GitHub repos. A larger team with a different workflow may not fit it yet.

Related