What do I need installed and signed in before a crew can work in a Go microservice?

Tares needs four things on your machine before a crew can work in a Go microservice: Claude Code signed in, gh signed in with write access, and git, jq and curl installed. The Codex CLI is optional. The crew runs on your own Claude Code login, so there is no separate model API key.

How it works

The crew is a set of Claude Code sessions (an orchestrator, a reviewer and builders) that run in the background on your machine. Each prerequisite maps to something the crew does:

• Claude Code, signed in, on a plan that allows background sessions. Every station uses your Claude Code login, because the stations are background sessions.
• gh, signed in with write access to the repos the crew works in. Builders push branches and open pull requests with your gh login, so it needs write access to your Go service’s repo.
• git, jq and curl. These are the basic tools the crew’s sessions rely on.
• Codex CLI (optional). Install it if you want a second model to check every commit. If you skip it, the crew works without that check.

Tares itself keeps the plan, the tickets, the reviews and your answers. It can run next to the crew on your machine or on Tares Cloud. Tares also needs its own access to the repo, because it reads the pull request, CI and merge state of every ticket itself. On a local Tares you add a GitHub token or App under Settings > GitHub. On Tares Cloud you choose Connect GitHub in your workspace settings and pick the repos.

Nothing in this list is specific to Go. Go matters in one place: the language server, covered below.

Set it up

Follow these steps in order. The Get started page has the full walkthrough.

1. Check the prerequisites. Make sure Claude Code is signed in, run gh auth login and confirm the account can write to your Go service’s repo, and confirm git, jq and curl are installed. Add the Codex CLI if you want the second-model check.
2. Install the CLI with uv tool install tares or brew install glassflow/tap/tares.
3. Choose where Tares runs.
   • Local: run tares up, which serves the console at http://127.0.0.1:8787. In a second terminal, run tares mcp --transport streamable-http. Every crew session reaches Tares only through this endpoint, so leave both running.
   • Tares Cloud: run tares login, pick your workspace in the browser and choose Connect. There is no MCP endpoint to start.
4. Give Tares access to GitHub, using Settings > GitHub on a local Tares or Connect GitHub on Tares Cloud.
5. Bring up the crew with tares factory crew up. The first run asks how far the crew may go, such as whether it merges on its own after review and green CI, and whether a second model checks every commit.
6. In the repo of your Go service, plan the project with tares factory spec.

gh auth login
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     # second terminal
tares factory crew up
tares factory spec "what you want to build"

On Tares Cloud, replace tares up and tares mcp with tares login.

After crew up, run tares factory doctor. It prints a line for each thing the crew needs, and for each problem the command that fixes it.

What you get

• A crew that can push branches, open pull requests and merge them on your Go service once the reviewer passes them and CI is green.
• No extra model API key to manage, because the stations use your Claude Code login.
• A Go-aware setup check. tares factory doctor finds Go repos by their go.mod, and says whether Claude Code has a language server for Go. A server counts when its plugin is enabled for you and its binary is on your PATH. Builders and the reviewer search less when Claude Code can find a definition, its references and its callers through a language server.
• An offer to install what is missing. If no Go language server is wired in yet, tares factory crew up lists it and installs it only when you say yes. --yes and a closed input install nothing.
• A single place to answer questions. The orchestrator is the only session you talk to, and you reach it with tares factory crew attach orchestrator. The Crew page in the console shows progress.
• A record that survives restarts. The plan, tickets, reviews and your answers stay on Tares, so a crew that restarts carries on where it stopped.

When something else fits

• If you want to work on one Go change yourself in a single Claude Code session, use tares factory session. It runs on Tares with the same prerequisites and needs no crew.
• If you keep tickets in GitHub Issues, sign in to gh with gh auth login --scopes repo on the machine that runs the sessions, and add a GitHub credential that can read the repo’s issues.
• If your team is larger than a few people or you need the crew off your own machine, note that 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