Where can I read back what the crew decided during internal refactors in a Python backend?

Tares keeps that record on the project page in the console. Open the project and unfold Decisions for your answers in your own words, Assumptions for the choices the crew made alone, Tickets for the work, and Sessions for the transcripts. The same folds apply to any project you hand to the software factory for Claude Code, including a refactor of a Python backend.

How it works

Every project you hand to the crew gets its own page, the record of the whole build. Four steps run across the top (Spec, Build, Review, Done) above a progress bar with one segment per ticket. Below that, each part of the record is a fold you open when you need it.

For the question of what was decided, four folds matter:

• Decisions lists every question the crew asked you, newest first, with your answer as you typed it. A recorded answer holds up to 4,000 characters.
• Assumptions lists every choice the crew made on its own when the plan did not cover something, and whether you kept it. Each one names the tickets it touches and the builder that made it.
• Tickets shows milestones with their acceptance checks. Each ticket shows the builder that held it, its pull request and its review rounds.
• Sessions holds the recorded Claude Code sessions, from the spec session to each builder.

You answer the crew’s questions in the orchestrator’s session. Tares then finds your reply in that session by matching it line by line, so a long pasted reply with several paragraphs matches in full. Tares keeps up to 20,000 characters of your turn for this match. An answer stored before Tares fixed this stays cut, so paste the missing lines once more.

The page follows the same layout for every project. The factory does not give a Python backend or a refactor a record of its own, so what you read back is the same trail you would see on any other project.

Set it up

1. Start Tares on your machine.

tares up

2. In a second terminal, start the MCP endpoint every crew session shares.

tares mcp --transport streamable-http

3. Bring up the crew, then plan the project from your repo. The spec session asks you questions, and the result goes into Tares as the spec, the plan and the milestones.

tares factory crew up
tares factory spec "what you want to build"

4. Answer the crew’s questions in the orchestrator’s session while it builds. Each answer lands in the Decisions fold as you typed it.
5. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. Open your project from the Projects list. Finished projects are folded below the open ones.
6. Unfold Decisions first, then Assumptions. At the end of each milestone the orchestrator brings you its assumptions in one question, so you can keep or reject them there. To make an answer stand from now on, say so, for this project or for every project.
7. Unfold Tickets and Sessions to see which builder held each ticket and to find the session behind it.

If you have not set up the crew before, start with Get started. For one real project followed from spec to done, with screenshots of each fold, read A project, end to end.

What you get

• A dated trail of every question the crew put to you, with your own wording kept intact.
• A list of the choices the crew made without asking, each tied to its tickets and its builder, with a note of whether you kept it.
• Tickets that show the builder, the pull request and the review rounds, so you can follow a change back to the decision behind it.
• Recorded sessions, from the spec session to each builder, for the detail behind a ticket.
• A record that stays after the work ends. Run tares factory crew down to stop every station. Tares keeps the projects, tickets and answers, so the crew carries on from them when you bring it back up.

The Docs fold also holds the starting prompt, the spec, the plan and the project’s AGENTS.md, so you can compare what you asked for with what the crew decided along the way. You can edit those docs from the page.

When something else fits

• To see what moved across projects, use Standup on the Crew page. It reports what is done, started, in review, blocked and waiting on you, since yesterday, over 7 days, or between dates you pick.
• To see what a single station is doing right now, click it on the Crew page for its tickets and last lines.

Related