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

Tares keeps that record on the project page in the console. The Decisions fold holds every question the crew asked you and your answer in your own words, and the Assumptions fold holds every choice the crew made on its own. The Tickets and Sessions folds complete the audit trail for a small feature 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:

• 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 assumption 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 lists the recorded Claude Code sessions, from the spec session to each builder.

You answer the crew’s questions in the orchestrator’s session. 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. A reply stored before Tares fixed this stays cut, so paste the missing lines once more.

When the crew meets something the plan does not cover, it picks the sensible answer, writes it down as an assumption and carries on. Mid-build, assumptions are still open. At the end of each milestone the orchestrator brings them to you together in one question, and your answer to that question lands in Decisions.

A Node/TypeScript project shows what this looks like. In the walkthrough project, the working doc named vitest.config.ts, which fails to load on the repo’s Node version, so the builder used vitest.config.mts and recorded it as an assumption. Another assumption recorded that the CI job for database tests ran on the same Node version as the unit tests. The project’s five questions, such as trusting the repo folder and giving Tares a GitHub token, sit in Decisions with the answers as typed. The full walkthrough is in A project, end to end.

Set it up

1. Hand the feature to the crew. If you are new to the factory, start with Get started. Bring up the crew, then plan the feature from the repo:

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

2. Answer Claude Code’s spec questions, then say yes to handing the project to the crew. The orchestrator picks it up and starts a builder.
3. Answer the crew’s questions in the orchestrator’s session as they come. Type your answer in full, in your own words. It is stored as you typed it, up to 4,000 characters.
4. Open the Crew page in the console (http://127.0.0.1:8787/crew locally). Open the project from the Projects list. Finished projects are folded below the open ones.
5. Open the Decisions fold to read every question and your answer, newest first.
6. Open the Assumptions fold to see each choice the crew made on its own, whether you kept it, and the tickets and builder behind it.
7. Open Tickets for the pull request and review rounds of each ticket, and Sessions for the recorded Claude Code sessions.
8. To make an answer stand from now on, say so in the session, for this project or for every project.

What you get

• One page that holds the whole record of a feature: the starting prompt, spec and plan in Docs, the tickets with their pull requests and review rounds, and the sessions.
• Your answers kept in your own words, with no summary written over them.
• A list of the choices the crew made without asking you. You see each one, and each one says whether you kept it.
• A record that stays after the work ends. When the last milestone is done, the orchestrator asks whether the project is finished, and Tares marks it Done with your words and moves it to the finished list. If you stop the crew with tares factory crew down, Tares keeps the projects, tickets and answers.
• A standup report, top right on the Crew page, that shows what is done, started, in review, blocked and waiting on you for each project, with pull request links.

When something else fits

• To follow a build as it happens rather than read it back, use the Crew page. It shows each station’s state, the questions waiting for you at the top, and the review queue.
• To see a short summary of what moved over a day or a week, use Standup. For the reasoning behind a specific choice, read Decisions and Assumptions.

Related