Skip to Content
Tares

Can a crew of Claude Code sessions handle small features in a Go microservice?

Yes, Tares runs a crew of Claude Code sessions that builds small features in a Go microservice into pull requests merged on main. The orchestrator starts one builder per milestone and repo, and every pull request needs the reviewer’s pass and green CI before it merges. Doctor also checks that Claude Code has a Go language server for the repo.

How it works

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

What changes with your repo:

  • Builder assignment. The orchestrator starts builders for each project, one per milestone and repo, up to the number you allow. A Go microservice in one repo gets one builder per milestone. If a feature touches a second repo, such as a shared library, that milestone and repo pair gets its own builder.
  • One ticket, one branch. Each builder takes a ticket, works on its own branch, opens a pull request and merges it once the reviewer passes it and CI is green.
  • What the pull request has to pass. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request. Your repo’s CI must also be green, so the build and test steps that count are the ones your CI runs for the service. The plan adds acceptance checks to each milestone, so you can also compare the result against the checks you agreed.
  • Go tooling. Builders and the reviewer search less when Claude Code can find definitions, references and callers through a language server. tares factory doctor finds a Go repo by its go.mod and reports whether Claude Code has gopls for it. For a missing server it prints what to run, and tares factory crew up offers the same install and runs it only when you say yes.

If you want a human check on a project, it can wait for your yes before every merge while the rest of the crew merges on its own.

Set it up

Start with the prerequisites from Get started: Claude Code signed in on a plan that allows background sessions, gh signed in with write access to the service repo, and git, jq and curl installed.

  1. Check GitHub access.
gh auth login
  1. Install the CLI and start Tares locally.
uv tool install tares     # or: brew install glassflow/tap/tares
tares up
  1. In a second terminal, start the MCP endpoint every crew session shares. On a local Tares the crew reaches Tares only through it.
tares mcp --transport streamable-http

On Tares Cloud, run tares login instead and pick your workspace in the browser. There is no MCP endpoint to start.

  1. Give Tares its own access to the repo. On a local Tares add a GitHub token or App under Settings > GitHub. On Tares Cloud choose Connect GitHub and pick the repo. Tares reads the pull request, CI and merge state of every ticket itself.

  2. Bring up the crew. The first run asks whether the crew merges on its own after review and green CI, whether it releases, whether a second model checks every commit, and how many builders run at once. If the Go repo has no language server wired in, it lists what is missing and offers to install it.

tares factory crew up
  1. In the service repo, plan the feature. Keep the plan small so it stays within a milestone or two.
tares factory spec "what you want to build"

Claude Code interviews you one question at a time and has a second model attack the plan. It then writes the spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md into a Tares project. Say yes when it asks whether to hand the project to the crew.

  1. Answer questions in the orchestrator’s session and run doctor whenever a station misbehaves.
tares factory crew attach orchestrator
tares factory doctor

What you get

  • Small features arrive as pull requests on their own branches, reviewed to a fixed bar, and merged on main once CI is green.
  • Builders are assigned per milestone and repo, so you can read the Crew page and see which builder holds which part of the service.
  • Every choice the crew makes on its own is written down, so you check it at the end of each milestone instead of during every step.
  • You talk to one session, the orchestrator, and questions reach you one at a time, each with a recommendation.
  • The crew works on several projects at once, so while one waits for you the others carry on.
  • Tares keeps the plan, tickets, reviews and your answers, so a restart does not lose progress.

When something else fits

  • For one small change, tares factory session with your idea plans a small project and builds it in your own Claude Code session, still recorded on Tares. If the plan turns out big, it offers the full spec and the hand-over to the crew.
  • The software factory is for solo developers and very small teams on one machine, using your own Claude Code login and your own GitHub repos.
  • If you want a release step, ask for a releaser. Without one, tickets end at merged on main.

Still stuck? Get help

Last updated on
Quickstart