What waits on my desk while the crew works on small features?

Tares puts the questions the crew cannot answer itself on your desk, and you read them with tares factory crew desk. You answer them in the orchestrator’s session, one at a time, each with a recommendation. Everything else the crew decides on its own and writes down for you to check later.

How it works

The desk is the list of questions waiting for you. The crew is an orchestrator, a reviewer and builders, and the orchestrator is the only session you talk to. When a builder or the reviewer needs a decision that is really yours, the question reaches you through the orchestrator.

• One at a time. Questions arrive in the orchestrator’s session singly, so you never face a pile in the terminal.
• Each with a recommendation. The orchestrator brings its suggested answer with every question, so you can accept it or say something different.
• From every project. One crew serves all the projects you hand it. Questions from each project reach you in the same orchestrator session, and while one project waits for you, the others carry on.
• Kept on Tares. Tares holds the questions the crew asked you and your answers in your own words. If a session restarts, the record stays and the crew carries on where it stopped.

Choices the crew makes without you are not on the desk. Tares records them as assumptions, so you can review them at the end of each milestone instead of during every step.

Set it up

1. Bring up the crew if it is not running. The Get started page lists the full setup, and the one command to remember is:

   tares factory crew up

2. Read what is waiting for you. This prints the questions on your desk, each in full:

   tares factory crew desk

3. For a quick overview, check the stations, the questions for you and a line per project:

   tares factory crew status

4. Open the orchestrator in your terminal and answer its questions there, one at a time. Read the recommendation that comes with each question and reply in your own words:

   tares factory crew attach orchestrator

5. Follow progress in the browser on the Crew page of the Tares console, at http://127.0.0.1:8787/crew on a local Tares. The question waiting for you is at the top, followed by the stations, each open project with its builders, and the pull requests waiting for review.

6. If something looks wrong, check everything the crew needs. Doctor prints a line for each item and the command that fixes any problem:

   tares factory doctor

What you get

• A short list of decisions that are yours, instead of terminals to watch.
• A recommendation with every question, so a quick answer is usually enough.
• One place to answer, the orchestrator’s session, however many projects the crew has open.
• A durable record on Tares of each question and your answer, which survives a crew restart.
• A written list of the assumptions the crew made on its own, ready to check at the end of each milestone.
• A live view on the Crew page that shows the waiting question first, next to each project’s builders and the pull requests waiting for review.

When something else fits

• If you want to work on a project yourself, with no crew asking you questions, use tares factory session to build it in your own Claude Code session on Tares.
• If you only need a glance at state, tares factory crew status is faster than reading each question in full.

Related