Can I take over test coverage from the crew halfway and finish it myself?

Yes, Tares lets you take a project over from the crew halfway and finish it in your own Claude Code session. You start the session with tares factory session and say yes when it asks whether to take the project over. The crew stops, and your session carries on from the branches and pull requests its builders left.

How it works

Takeover works on a whole project, not on a single ticket. If your test coverage work is a project the crew has, you take over that project.

• The crew is an orchestrator, a reviewer and builders. Each builder works a ticket on its own branch and opens a pull request.
• Tares keeps the plan, the tickets and their stages, every review, the assumptions the crew made and your answers. The record stays on Tares, so your session starts from it and not from nothing.
• tares factory session <project> opens Claude Code with the Tares plugin, bound to that project. When the crew has the project, the session asks whether to take it over.
• If you say yes, the crew stops. Its builders push what they have and write their progress, and your session continues from their branches and pull requests.
• If you say no, the crew keeps the project.

Start these sessions through tares factory session. A plain claude has no Tares tools, so it cannot work on a project the way the session command does. Your shared AGENTS.md and memory apply in the session, and the session’s record lands on the project.

Set it up

1. Make sure the crew is running and the project is handed to it. If you have not set up the crew yet, follow Get started.

2. List the projects the crew has, with their progress, builders and repos:

   tares factory projects

3. Open your own session on the project. Use the project name from the list:

   tares factory session <project>

   You can also run tares factory session with no argument and pick the project, or start something new.

4. When the session asks whether to take the project over, say yes. The crew stops, and its builders push their work and write down their progress.

5. Read the branches and pull requests the crew left, then finish the remaining work in the session. The session reads the project’s tickets and works the ready ones.

6. When the project is done, you can mark it finished yourself:

   tares factory finish <project> "<words>"

   The words are your note on why it is done.

If your tickets live in Linear or GitHub Issues, the session updates them with its own tools. Tares only reads them, about once a minute, to keep the project’s ticket list in step.

What you get

• You finish the work in your own Claude Code session, with a say in every step instead of answering questions from a crew.
• You start from the branches and pull requests the builders left, so nothing already built is thrown away.
• The crew stops, so it does not keep pushing or opening pull requests on the same project while you work.
• The builders write their progress before they stop, so you can see where they got to.
• The plan, the tickets, the reviews and the assumptions the crew made stay on the project in Tares, and your session’s record is added to them.
• Other projects are not part of the takeover. It happens one project at a time, when you say yes at the prompt.

When something else fits

• If you only want to see or steer the work, stay with the crew. Say no at the takeover prompt, or open the orchestrator with tares factory crew attach orchestrator and answer its questions.
• If you only need the crew to pause, tares factory crew halt "<reason>" stops merges, pushes and new sessions until tares factory crew resume. It is a pause, not a handover to you.
• If the work is small and new, tares factory session "<idea>" plans and builds it in your own session without the crew.

Related