What waits on my desk while the crew works on bug fixes?

Tares puts the questions the crew cannot answer itself on your desk, and you read them with tares factory crew desk. While the software factory for Claude Code works on your bug fixes, each question waits there with a recommendation until you answer it in the orchestrator’s session. Questions arrive one at a time, and the rest of the crew keeps working while you decide.

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 orchestrator brings it to you.

• One session for every question. Questions from every project reach you in the orchestrator’s session, one at a time. Each comes with a recommendation, so you can accept it or answer in your own words.
• The record lives on Tares. Tares holds the plan, the tickets and their stages, every review, the assumptions the crew made, the questions it asked you, and your answers in your own words. The sessions come and go, and a crew that restarts carries on where it stopped.
• Other work carries on. When one project waits for you, the others keep going. Builders keep working their own tickets, and the reviewer keeps reviewing pull requests.
• Merges can wait for you too. At first run of crew up, you choose whether the crew merges on its own after review and green CI or waits for your yes. A single project can also wait for your yes before every merge, even when the rest of the crew merges on its own.

The desk works the same way for a project made of bug fixes as for any other project the crew has.

Set it up

You need the crew running and a project handed to it. The full walkthrough is on the Get started page.

1. Start Tares and the MCP endpoint that every crew session shares. On a local Tares, run these in two terminals and leave them running. On Tares Cloud, run tares login instead and skip the MCP endpoint.

   tares up
   tares mcp --transport streamable-http

2. Bring up the crew from a third terminal.

   tares factory crew up

3. Plan the project in the repo it builds on. Describe the bug fixes you want. The planning session ends by asking whether to hand the project to the crew. Say yes, and the orchestrator picks it up.

   tares factory spec "what you want to build"

4. Check what is waiting. crew status shows the stations, the questions for you and a line per project. crew desk shows each waiting question in full.

   tares factory crew status
   tares factory crew desk

5. Open the orchestrator in your terminal and answer. Take the questions in the order they arrive, one at a time, and read the recommendation that comes with each.

   tares factory crew attach orchestrator

6. Watch progress 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 sits at the top, followed by the stations, each open project with its builders, and the pull requests waiting for review.

If a station misbehaves or a question does not reach you, run tares factory doctor. It prints a line for each thing the crew needs and the command that fixes each problem.

What you get

• A short list that is only yours. The desk holds decisions the crew cannot make itself, so you are not watching terminals or reading every step.
• A recommendation with every question. You can agree in a word or give your own answer.
• A clear place to answer. The orchestrator is the one session you talk to, so questions never come from several sessions at once.
• Your answers kept in your words. They are stored on Tares with the plan, the tickets, the reviews and the assumptions the crew made on its own.
• Checks at the end of a milestone. Every choice the crew made without you is written down, so you can review those at the end of each milestone instead of during every step.
• Progress while you are away. Other projects and tickets keep moving while a question waits for you.

When something else fits

• If you only want to fix one bug in a Claude Code session of your own, use tares factory session. It works on a project, or plans a small one and builds it right there, with no crew and so no desk.
• If a project is already done in your eyes, mark it finished yourself with tares factory finish, rather than answering more questions.

Related