Where can I read back what the crew decided during dependency upgrades in a Python backend?

Tares keeps every project you hand to the crew on its own project page, and the Decisions and Assumptions folds there hold what the crew decided during your dependency upgrades. Decisions lists each question the crew asked you with your answer in your own words. Assumptions lists each choice the crew made on its own and whether you kept it. Tickets and Sessions on the same page complete the audit trail.

How it works

The software factory for Claude Code records the whole build on one project page. Open the Crew page in the console (http://127.0.0.1:8787/crew locally), pick the project, and its parts fold open one by one:

• Decisions holds every question the crew asked you and your answer, in your own words, newest first. A recorded answer holds up to 4,000 characters.
• Assumptions holds 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 holds the milestones with their acceptance checks, and each ticket with 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.
• Docs holds the starting prompt, the spec, the plan and the project’s AGENTS.md.

You answer the crew’s questions in the orchestrator’s session. The answer goes into the Decisions fold as you typed it. Tares matches your answer in your session line by line, so a long pasted reply with several lines or paragraphs is kept in full.

Assumptions stay open while a milestone is building. At the end of each milestone, the orchestrator brings you its assumptions in one question, and your reply is recorded with them. To make an answer stand from now on, say so, for this project or for every project.

Set it up

Hand your Python backend upgrade to the crew, then read the record on its project page. The full walk-through of a finished project is in A project, end to end, and Get started covers the setup in detail.

1. Check that Claude Code is signed in, gh is signed in with write access to the repos the crew works in, and git, jq and curl are installed.
2. Install the CLI, start Tares locally, and start the MCP endpoint every crew session shares in a second terminal. Then bring up the crew and plan the project:

uv tool install tares     # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "upgrade the dependencies of the Python backend"

3. Answer Claude Code’s questions in the spec session. At the end, say yes to handing the project to the crew.
4. Answer the crew’s questions in the orchestrator’s session as they come. Each answer lands in the Decisions fold.
5. Open the project from the Crew page. Open projects are listed with their builders, and finished ones are folded below.
6. Open Decisions to read your answers, then Assumptions to see what the crew chose on its own. Use Tickets and Sessions to trace a decision back to the pull request and the session that produced it.

On Tares Cloud, sign in with tares login instead of starting Tares and the MCP endpoint locally.

What you get

• One page per project that records the whole build, from the spec to done, so you can read back each decision later.
• Your answers in your own words, not a summary. Each is kept up to 4,000 characters.
• A list of the choices the crew made without asking you, each tied to the tickets it touches and the builder that made it, and marked kept or not.
• A trail from decision to code: the ticket, the builder that held it, its pull request and its review rounds, plus the recorded session of each builder.
• A durable record. After tares factory crew down stops the stations, Tares keeps the projects, tickets and answers, so the crew carries on from them when you bring it back up.
• In a finished project, the five questions and the assumptions sit in their folds, and Tares marks the project Done with the words you gave when you said it was finished.

The folds are the same for every project, so the page for your upgrade work reads like the page for any other build.

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.
• If you track work in Linear or GitHub Issues, the crew’s sessions update those tickets with their own tools. Tares reads them and keeps its own record on the project page.
• To see a code change itself, open its pull request from the Tickets or GitHub fold.

Related