Where can I read back what the crew decided during bug fixes in a Python backend?

Tares keeps every decision the crew made on your project in the project page, so you can read it back at any time. The Decisions fold lists every question the crew asked you and your answer in your own words, newest first. The Assumptions fold lists every choice the crew made on its own and whether you kept it. Tickets and Sessions folds sit beside them as the rest of the record.

How it works

Every project you hand to the software factory for Claude Code gets a page of its own, the record of the whole build. For bug fixes in a Python backend, that page is where you read back what happened. Each part of the record folds open:

• Decisions: every question the crew asked you and your answer, in your own words, newest first. Each answer is kept as you typed it.
• Assumptions: every choice the crew made on its own when the plan did not cover something, and whether you kept it. Each assumption names the tickets it touches and the builder that made it.
• Tickets: milestones with their acceptance checks, and each ticket with the builder that held it, its pull request and its review rounds.
• Sessions: the recorded Claude Code sessions, from the spec session to each builder.
• Docs, GitHub and Crew: the starting prompt, spec, plan and AGENTS.md, the repos and pull requests, and the stations that worked on the project.

You answer the crew’s questions in the orchestrator’s session. Some are steps only you can take, and some come at the end of each milestone, when the orchestrator brings you its assumptions in one question. If a project waits for your yes before every merge, most of its decisions are merge approvals, each with the answer as typed.

Set it up

1. Install Tares and start it locally.

uv tool install tares                # or: pipx install tares
tares up

2. Hand your Python backend repo to the crew. Run the spec command in the repo and answer Claude Code’s questions. The result goes into Tares as a spec, a plan, an AGENTS.md for the project and milestones with acceptance checks.

tares factory spec

3. Start the crew, then answer its questions in the orchestrator’s session as the bug fixes progress.

tares factory crew up

4. Open the Crew page in the console at http://127.0.0.1:8787/crew and click into your project to reach its page.
5. Open the Decisions fold to read each question and your answer, newest first. Open Assumptions to see what the crew chose on its own and whether you kept it.
6. Open Tickets to see each ticket with its builder, pull request and review rounds, and Sessions to see the recorded Claude Code sessions.
7. To make an answer stand from now on, say so, for this project or for every project.

If you want to read the plan the crew followed, open the Docs fold. All docs lists the starting prompt, spec, plan and AGENTS.md, and you can edit any of them there. For the full walkthrough of a finished project, see A project, end to end.

What you get

• A record of every question the crew asked you, with your answer in your own words, newest first.
• A list of every choice the crew made on its own, with whether you kept it, and for each one the tickets it touches and the builder that made it.
• Tickets that show the builder, pull request and review rounds, so you can see how each bug fix was reviewed and merged.
• The recorded Claude Code sessions, from the spec session to each builder.
• A project that Tares marks Done with your own closing words once every ticket is merged. Tares keeps the projects, tickets and answers after you stop the crew, so you can read them back later.

When something else fits

• If you want to read back the full text of what a builder did, open the Sessions fold for the recorded Claude Code sessions.
• If you are new to the factory, start with Get started before you read a finished project’s record.

Related