What waits on my desk while the crew works on framework migrations?

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. Hand the crew a framework migration as a project and it works the same way as for any other project.

How it works

The crew is an orchestrator, a reviewer and builders, all Claude Code sessions running in the background on your machine. The orchestrator is the only session you talk to. When a builder or the reviewer hits a decision that is yours, the orchestrator brings it to you.

The desk is the list of those waiting questions. Tares holds the questions the crew asked you and your answers in your own words, together with the plan, the tickets, every review and the assumptions the crew made. The sessions come and go, but the record stays on Tares, so a crew that restarts carries on where it stopped.

A few points about how the desk behaves:

• Questions from every project reach you in the orchestrator’s session, one at a time.
• Each question comes with a recommendation, so you can accept it or say something different.
• While one project waits for you, the others carry on.
• Choices the crew made on its own are written down, so you can check them at the end of each milestone instead of during every step.
• If you set a project to wait for your yes before every merge, that project waits on you even when the rest of the crew merges on its own.

You see this the same way for a framework migration as for any other project handed to the crew. Read more about the crew in Get started.

Set it up

1. Check that Claude Code is signed in, that gh is signed in with write access to the repos the crew works in, and that git, jq and curl are installed.

2. Install the CLI and start Tares locally. On Tares Cloud, run tares login instead and pick your workspace in the browser.

   uv tool install tares     # or: brew install glassflow/tap/tares
   tares up

3. On a local Tares, start the MCP endpoint every crew session shares, in a second terminal.

   tares mcp --transport streamable-http

4. Bring up the crew.

   tares factory crew up

5. Plan the migration as a project, in the repo it builds on. Say yes when it asks whether to hand the project to the crew.

   tares factory spec "what you want to build"

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

   tares factory crew desk
   tares factory crew status

7. Open the orchestrator in your terminal and answer the questions there, one at a time.

   tares factory crew attach orchestrator

8. Follow 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.

To see every project handed to the crew with its progress, builders and repos, run tares factory projects. If something looks wrong, run tares factory doctor to check everything the crew needs.

What you get

• One place to look. The desk lists what needs you, so you do not watch terminals.
• One place to answer. Questions from every project arrive in the orchestrator’s session, one at a time, each with a recommendation.
• A short desk. You decide only what is really yours, while the crew works the tickets into pull requests, the reviewer holds every change to a fixed bar, and builders merge once the reviewer passes it and CI is green.
• A record. Your answers are kept in your own words on Tares next to the plan, tickets and reviews, and the crew’s own assumptions are written down for you to check at the end of each milestone.
• Live visibility. The Crew page shows the waiting question, each station and each project’s builders, so you can see where the work stands before you answer.

When something else fits

• If you want to work a small project yourself rather than hand it to a crew, run tares factory session, which opens your own Claude Code session bound to the project. It can take a project over from the crew when you say yes.
• If you only want a quick overview rather than each question in full, tares factory crew status gives the stations, the questions for you and a line per project.
• If you want to stop all merges and pushes while you sort something out, use tares factory crew halt with a reason, then tares factory crew resume when you are ready.

Related