Can I take over small features from the crew halfway and finish it myself?

Yes, Tares lets you take over a project the crew is working on and finish it in your own Claude Code session. You say yes when the session asks, the crew stops, and your session carries on from the branches and pull requests the builders left. Takeover works on a whole project, so a small project is the natural fit.

How it works

The crew is an orchestrator, a reviewer and builders, all Claude Code sessions on your machine. Tares holds the plan, the tickets and their stages, every review, the assumptions the crew made and your answers. Because that record lives on Tares and not in the sessions, a session you start yourself can pick up where the crew left off.

You start your own session with tares factory session, which opens Claude Code with the Tares plugin and binds it to a project. When the project is one the crew has, the session asks whether to take it over:

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

The unit you take over is a project, not a single ticket or feature. A small feature that is its own project, or a small project with a few tickets, is a good candidate. If the work you want is one ticket inside a larger project, the takeover still covers the whole project.

Your session works on Tares like the crew does. Your shared AGENTS.md and memory apply, and the session’s record lands on the project. A plain claude has no Tares tools, so start these sessions with tares factory session.

Set it up

1. Make sure Tares is running. On a local Tares that means tares up in one terminal and tares mcp --transport streamable-http in a second one, because every session reaches Tares through the MCP endpoint. On Tares Cloud you sign in with tares login instead.
2. See what the crew has and how far each project is:

tares factory projects

3. Open your own session on the project you want to finish:

tares factory session <project>

4. When the session asks whether to take the project over, say yes. The builders push their work and write their progress, then the crew stops.
5. Work the remaining tickets from the existing branches and pull requests. Push to the branches and open or update pull requests as you normally would.
6. If you finish the project outside a ticket flow, mark it done yourself with a short note:

tares factory finish <project> "<words>"

If you run tares factory session with no argument, it lets you pick a project or start something new. If you run it with a quoted idea, it plans a small project and builds it in your session, so you can start small work yourself without the crew. For the full crew setup, see Get started.

What you get

• A clean handover. The builders push their work and write their progress before the crew stops, so you do not start from a half-finished local state.
• Your starting point is real work. You continue from the crew’s branches and pull requests, not from a blank page.
• The record stays whole. The plan, tickets, reviews, assumptions and your earlier answers stay on Tares, so your session reads the same project the crew did.
• Your choice at the prompt. Answer no and the crew keeps the project, so asking costs you nothing.
• Finish on your terms. You can finish the tickets in your session or mark the project done with tares factory finish.

When something else fits

• If you only want to steer the crew, stay in the orchestrator with tares factory crew attach orchestrator and answer its questions. The crew keeps building.
• If the project is small from the start, plan it with tares factory session and an idea. Your session builds it directly and offers the crew hand-over only when the plan turns out big.

Related