Can I take over framework migrations from the crew halfway and finish it myself?

Yes, Tares lets you take over a project the crew is working on, such as a framework migration, and finish it in your own Claude Code session. When you say yes, the crew stops, its builders push what they have and write their progress, and your session carries on from their branches and pull requests. Say no and the crew keeps the project.

How it works

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

That record is what makes a mid-project handover work.

• You open your own Claude Code session bound to the project with tares factory session. A plain claude has no Tares tools, so start the session this way.
• Because the crew already 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.
• Your session carries on from the branches and pull requests the crew left.
• If you say no, the crew keeps the project and nothing changes.

Your session still runs on Tares, so your shared AGENTS.md and memory apply, and the session’s record lands on the project. The Get started page has the full setup for the crew and for single sessions.

Set it up

1. Make sure Tares is running and the crew has your project. On a local Tares, tares up and tares mcp --transport streamable-http stay running, because every session reaches Tares through the MCP endpoint. Check what the crew holds:

tares factory projects

2. Look at the stations and the questions waiting for you, so you know where the crew stands before you step in:

tares factory crew status

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

tares factory session <project>
tares factory session               # pick one, or start something new

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

5. Finish the work in that session. Review the open pull requests the crew left, continue the unfinished tickets on their branches, and merge as you normally would.

6. When you are done, mark the project finished yourself:

tares factory finish <project> "<words>"

If the project’s tickets live in Linear or GitHub Issues, your session updates them with its own tools. Tares reads them and never writes to them.

Run tares factory doctor if a station or session misbehaves. It prints a line for each thing the crew needs and the command that fixes each problem.

What you get

• You finish the migration yourself, in your own Claude Code session, without starting over.
• You keep the crew’s work: its branches, its pull requests and the progress its builders wrote down before they stopped.
• The crew stops when you take the project over, so it does not push against your changes.
• The plan, tickets, reviews, assumptions and your earlier answers stay on the project in Tares, and your session adds its own record there.
• Your shared AGENTS.md and memory apply in the session, the same as they did for the crew.
• The choice is yours at the prompt. If you say no, the crew keeps the project.

When something else fits

• If you only want to follow along, leave the crew in charge, say no at the prompt, and use tares factory crew attach orchestrator to answer its questions.
• If you want the crew to stop everything for a while without handing the project to yourself, tares factory crew halt stops merges, pushes and new sessions until tares factory crew resume.
• If a project is small, you can skip the crew and plan and build it in one session with tares factory session and your idea.

Related