Skip to Content

Where can I read back what the crew decided during framework migrations in a Go microservice?

Tares keeps every decision the crew takes on a project in the project page, so you read it back there. The Decisions fold holds each question the crew asked you with your answer in your own words, and the Assumptions fold holds each choice the crew made alone and whether you kept it. Tickets and Sessions sit on the same page, so the whole record of a framework migration in a Go microservice is in one place.

How it works

Every project you hand to the software factory for Claude Code gets a page of its own. Across the top are four steps (Spec, Build, Review, Done) and a progress bar with one segment per ticket. Below them, seven folds open one by one:

  • Docs: the starting prompt, the spec, the plan and the project’s AGENTS.md, plus the AGENTS.md and memory shared by every project.
  • Tickets: milestones with their acceptance checks, and each ticket with the builder that held it, its pull request and its review rounds.
  • GitHub: the repos the project changes, where each is checked out, and its open and merged pull requests.
  • Decisions: every question the crew asked you and your answer, newest first.
  • Assumptions: every choice the crew made on its own.
  • Crew: the stations that worked on this project.
  • Sessions: the recorded Claude Code sessions, from the spec session to each builder.

Decisions and Assumptions are the audit trail. When the crew needs something only you can give, it asks in the orchestrator’s session. You type the answer there, and it lands in the Decisions fold exactly as you typed it. A recorded answer holds up to 4,000 characters. Tares matches your answer in your session line by line, so a long pasted reply with several paragraphs matches in full.

When the crew meets something the plan does not cover, it picks a sensible answer, writes it down as an assumption and carries on. At the end of each milestone the orchestrator brings you its assumptions in one question, and your reply says which you keep. Mid-build they show as open, each with the tickets it touches and the builder that made it.

Set it up

  1. Check that Claude Code is signed in, that gh is signed in with write access to the repos the crew works in, and that git, jq and curl are installed.
  2. Install the CLI with uv tool install tares, or brew install glassflow/tap/tares.
  3. 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 instead and pick your workspace in the browser.
  4. Give Tares access to GitHub, in Settings > GitHub for a local Tares or with Connect GitHub on Tares Cloud.
  5. Bring up the crew with tares factory crew up.
  6. In your Go repo, plan the work with tares factory spec, and describe the migration you want. Claude Code asks you questions, and the result goes into Tares as a spec, a plan, an AGENTS.md and milestones.
tares factory crew up
tares factory spec "what you want to build"
  1. Say yes when asked to hand the project to the crew. Open the console at http://127.0.0.1:8787/crew on a local Tares, click the project under Projects, and open the Decisions fold. Open Assumptions next to it when a milestone ends.

A question that blocks work also shows at the top of the Crew page, under questions waiting for you. The finished projects stay in the list folded below the open ones, so you can read the record after the work is done.

What you get

  • One place to read what was settled. Each question the crew put to you sits beside your answer, in your words and newest first, so you see why a path was taken without reading a whole session.
  • A list of the crew’s own calls. Each assumption names its tickets and its builder, and shows whether you kept it. In the project followed on A project, end to end, the builder swapped a config file that would not load on the repo’s Node version and recorded that as an assumption. The same page also shows a pull request description rewritten instead of appended to.
  • A trail from decision to code. The Tickets fold links each ticket to its builder, pull request and review rounds, and the Sessions fold holds the recorded Claude Code sessions behind them.
  • Answers that outlast the crew. When you run tares factory crew down, Tares keeps the projects, tickets and answers, so the next tares factory crew up carries on from them.
  • A way to make a choice stick. Say so in your reply, for this project or for every project, and an answer stands from then on.

The Get started page walks through the first project from install to the first handoff.

When something else fits

  • If you only want a summary of what moved, the Standup report on the Crew page lists what is done, started, in review, blocked and waiting on you, with pull request links.
  • If you need to see how a specific change was made, open its ticket and its pull request. The Decisions fold records what you were asked, not the code diff.
  • To change the plan or steer the work, talk to the orchestrator instead of editing the record.

Still stuck? Get help

Last updated on