What waits on my desk while the crew works on docs updates?

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, while the crew keeps working on your docs updates project. The desk holds only what needs you, so you do not have to watch terminals.

How it works

The crew for your docs updates project is a set of Claude Code sessions on your machine: an orchestrator, a reviewer and builders. The orchestrator is the only session you talk to. It hands out work, answers the other sessions, and brings you what needs you.

When a decision is really yours, the question lands on your desk. Tares keeps the record of the plan, the tickets, the assumptions the crew made, the questions it asked you, and your answers in your own words. The sessions come and go, and the record stays on Tares, so a crew that restarts carries on where it stopped.

If you run several projects, questions from all of them reach you in the same orchestrator session, one at a time. While one project waits for you, the others carry on.

The desk shows:

• The questions waiting for you, each in full.
• On the Crew page of the console, the question waiting for you at the top, then the stations, each open project with its builders, and the pull requests waiting for review.

Set it up

Start the crew if it is not running, then read and answer the desk. For the full first-time setup, see Get started.

1. Bring up the crew. The first run asks how far the crew may go, such as whether it merges on its own after review and green CI or waits for your yes.

   tares factory crew up

2. Plan the docs updates project in the repo it builds on. The plan is written into a Tares project, and you hand it to the crew when asked.

   tares factory spec "what you want to build"

3. Read what is waiting for you. This lists the questions on your desk, each in full.

   tares factory crew desk

4. For a shorter view, check the stations, the questions for you and a line per project.

   tares factory crew status

5. Open the orchestrator in your terminal and answer. Questions arrive one at a time, each with a recommendation, so you can accept it or give your own answer.

   tares factory crew attach orchestrator

6. Follow progress on the Crew page of the console. On a local Tares it is at http://127.0.0.1:8787/crew.

7. If something looks wrong, run the check. It prints a line for each thing the crew needs and the command that fixes each problem.

   tares factory doctor

What you get

• One place to look. The desk lists every question that needs you, so you do not scan terminals for them.
• One conversation. You answer in the orchestrator’s session, one question at a time, and each comes with a recommendation.
• A record of your decisions. Your answers are kept on Tares in your own words, next to the plan, the tickets, the reviews and the assumptions the crew made.
• Fewer interruptions. The crew decides what it can on its own and writes those choices down, so you can check them at the end of each milestone instead of during every step.
• Steady progress. The builders keep working on the docs updates tickets, and the reviewer reviews every pull request, while you read the desk.

When something else fits

• If you want a project to wait for your yes before every merge, set that when tares factory crew up asks how far the crew may go. Pull requests then wait on you as well as questions.
• If a small docs change does not need a crew, work on it in your own Claude Code session with tares factory session, still on Tares.

Related