Where can I read back what the crew decided during dependency upgrades in a Node/TypeScript app?

Tares keeps what the crew decided on the project’s own page, in the Decisions and Assumptions folds. Decisions holds each question the crew asked you with your answer in your own words. Assumptions holds each choice the crew made on its own, and whether you kept it. Tickets and Sessions complete the audit trail for a dependency upgrade project in a Node/TypeScript app.

How it works

Every project you hand to the crew gets a page of its own, the record of the whole build. Each part of the record folds open. Four folds answer your question:

• Decisions lists 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 lists every choice the crew made on its own, 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, 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.

You answer the crew’s questions in the orchestrator’s session. 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. The answer lands in the Decisions fold as you typed it.

When the crew meets something the plan did not cover, it picks the sensible answer, writes it down as an assumption and carries on. Mid-build, assumptions stay open. At the end of each milestone the orchestrator brings them to you together in one question, and you keep or change them.

The A project, end to end walkthrough shows this on a real Node project. Its assumptions record that a config file named in the working doc failed to load on the repo’s Node version, so the builder used a different file name. Another records that the CI job for database tests ran on the same Node version as the unit tests. Choices like these, made while you upgrade dependencies, are the kind of thing you read back in Assumptions.

Set it up

1. Open the Crew page in the console, http://127.0.0.1:8787/crew on a local Tares. Open projects are listed under Projects, and finished ones are folded below.
2. Click your dependency upgrade project to open its project page. The four steps across the top, Spec, Build, Review and Done, and a progress bar with one segment per ticket show where it stands.
3. Open Decisions to read each question and your answer as you typed it. Open Assumptions to see what the crew chose on its own and whether you kept it.
4. Open Tickets to see which builder held each upgrade ticket, its pull request and its review rounds. Open Sessions to go back to the recorded Claude Code sessions.
5. To make an answer stand from now on, say so in the orchestrator’s session, for this project or for every project.

If you have no project yet, set up the crew first. On a local Tares the order is below. On Tares Cloud you run tares login instead of the first two lines, and there is no MCP endpoint to start. Get started covers the prerequisites and each step.

tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

Run tares mcp --transport streamable-http in a second terminal. In the spec, describe the dependency upgrades you want and answer Claude Code’s questions. Once you say yes to handing the project to the crew, the project page starts to fill.

What you get

• One page per project that records the whole build, so you do not have to dig through terminals to learn why something changed.
• Your answers kept in your own words, newest first, up to 4,000 characters each.
• Every choice the crew made on its own, listed as an assumption with its tickets and the builder that made it, and whether you kept it.
• Tickets with their builder, pull request and review rounds, so you can trace each change to the session that made it.
• A record that lasts. When you run tares factory crew down, Tares keeps the projects, tickets and answers, so the crew carries on from them next time. Finished projects stay in the folded list on the Crew page.

When something else fits

• To see what moved across projects, such as what is done, in review, blocked or waiting on you, open Standup on the Crew page instead of a single project page.
• To see who is working right now and what a station needs from you, use the Crew page and the station’s detail.

Related