Skip to Content

Can I take over internal refactors from the crew halfway and finish it myself?

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

How it works

The software factory for Claude Code runs a crew of background sessions: an orchestrator, a reviewer and builders. Each builder works a ticket on its own branch, opens a pull request, and merges it once the reviewer passes it and CI is green. Tares holds the plan, the tickets and their stages, every review, the assumptions the crew made and your answers. The record stays on Tares while sessions come and go.

A takeover uses that record. When you open a session on a project the crew currently has, the session asks whether to take it over.

  • You say yes: the crew stops. Its builders push what they have and write their progress. Your session carries on from their branches and pull requests.
  • You say no: the crew keeps the project and nothing changes.

Your session is a normal Claude Code session bound to the project. Your shared AGENTS.md and memory apply, and the session’s record lands on the project in Tares. A plain claude has no Tares tools, so start the session with the command below.

Set it up

  1. Check that the crew’s setup is healthy and that Tares is reachable. On a local Tares, keep tares up and the MCP endpoint running. On Tares Cloud, sign in with tares login. If anything looks wrong, run tares factory doctor; it prints the command that fixes each problem.

  2. List the projects the crew has, with their progress, builders and repos, and find the refactor you want:

    tares factory projects
  3. Open your own Claude Code session on that project:

    tares factory session <project> # work on a planned project

    You can also run tares factory session with no argument and pick the project from a list.

  4. When the session asks whether to take the project over, say yes. The crew stops, the builders push their work and write their progress, and the session starts from their branches and pull requests.

  5. Work the remaining tickets in your session. The pull requests the crew left are the starting point, so you continue them instead of redoing them.

  6. When the refactor is done, mark the project finished yourself:

    tares factory finish <project> "<words>"

    Replace the placeholders with your project and a few words on how it ended.

If you want to watch the crew before you decide, tares factory crew status shows the stations, the questions waiting for you and a line per project. You can also answer a waiting question first with tares factory crew attach orchestrator.

The full crew setup is on the Get started page.

What you get

  • A clean hand-over. The crew stops when you say yes. Builders push their work and write their progress first, so nothing is left only in a running session.
  • No lost work. Your session continues from the existing branches and pull requests, not from a blank start.
  • Your own session. You work in Claude Code with your AGENTS.md and memory, and the session’s record is stored on the project in Tares.
  • The full record. The plan, tickets, reviews, assumptions and your earlier answers stay on Tares for you to read as you finish.
  • A choice. If you say no at the prompt, the crew keeps the project and carries on.
  • Other projects keep going. One crew serves many projects, so taking over one project does not take the others from the crew.

When something else fits

  • If you only want to steer the work, leave the project with the crew. Answer its questions through tares factory crew attach orchestrator, or use tares factory crew halt to stop merges, pushes and new sessions until crew resume.
  • If you want every merge to wait for your yes, set that for the project and let the crew keep building. You review each change but do not write it.
  • If you want to stop all crew work, tares factory crew down stops every station. Tares keeps the projects, tickets and answers.

Still stuck? Get help

Last updated on