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

Tares keeps the record on the project page, which you open from the Crew page in the console. The Decisions fold lists every question the crew asked you and your answer, in your own words, and the Assumptions fold lists every choice the crew made on its own. Tickets and Sessions sit on the same page, so the dependency upgrades in your monorepo have one audit trail.

How it works

Every project you hand to the crew gets a page of its own, the record of the whole build. For your dependency upgrades, the folds below hold the decisions and the work around them:

• 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.
• GitHub lists the repos the project changes, where each is checked out, and their open and merged pull requests.
• Crew lists the stations that worked on the project, and 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, and the answer goes into the Decisions fold as you typed it. Tares finds your answer in your session by matching it line by line, so a long pasted reply with several lines or paragraphs matches in full. Tares keeps up to 20,000 characters of your turn for this, and the tags Claude Code wraps around pasted text do not stop a match.

At the end of each milestone, the orchestrator brings you its assumptions in one question. Until then they show as open.

Set it up

1. Check that the crew is running and see which projects it holds.

tares factory crew status

2. Open the Crew page in the console, at http://127.0.0.1:8787/crew on a local Tares. Under Projects, open projects are listed with their builders, and finished ones are folded below.
3. Open the project page for your dependency upgrades. The four steps across the top (Spec, Build, Review, Done) and the progress bar, with one segment per ticket, show how far the build has come.
4. Open Decisions to read each question and your answer, newest first. If a long pasted reply was stored before Tares fixed the matching and still shows cut, paste the missing lines once more.
5. Open Assumptions to read each choice the crew made on its own, the tickets it touches, the builder that made it and whether you kept it. To make an answer stand from now on, say so, for this project or for every project.
6. Open Tickets to see each ticket’s state (to do, in progress, in review, merged or blocked), its builder, its pull request and its review rounds. A blocked ticket names the tickets it waits for.
7. Open Sessions to read back the recorded Claude Code sessions, from the spec session to each builder. If the project touches several repos, GitHub shows each one and where it is checked out.

For a full walk through one project, see A project, end to end. To start a project of your own, see Get started.

What you get

• One page that records the whole build, from the starting prompt to Done.
• Your answers kept in your own words, so you read back what you decided and not a summary of it.
• A list of every choice the crew made without asking you, each with the tickets it touches and the builder that made it, and whether you kept it.
• Tickets with their builder, pull request and review rounds, so you can see how the work was reviewed and merged.
• Recorded sessions you can read back, from the spec session to each builder.
• The record stays after the project finishes. Tares keeps the projects, tickets and answers, and a finished project moves to the folded list on the Crew page.

When something else fits

• If you want a summary of what moved rather than the full record, use Standup on the Crew page. It reports what is done, started, in review, blocked and waiting on you, since yesterday, over the last 7 days or between dates you pick.
• If you need a decision that has not been asked yet, talk to the orchestrator. Questions waiting for you appear at the top of the Crew page and on the project page.

Related