Can I take over dependency upgrades from the crew halfway and finish it myself?

Yes, Tares lets you take a project over from the crew 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. This works for your dependency upgrades project the same way it works for any project the crew holds.

How it works

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

• You say yes. The crew stops working on the project. Its builders push their current work and write down their progress.
• Your session continues. It carries on from the branches and pull requests the builders left, so you do not start the dependency upgrades again.
• You say no. The crew keeps the project and nothing changes.

Tares holds the plan, the tickets and their stages, every review, the assumptions the crew made, the questions it asked you and your answers. Your session works against that record, so what the crew decided about the upgrades is still there when you pick up. Your shared AGENTS.md and memory apply, and your session’s record lands on the project.

Start these sessions with tares factory session. A plain claude has no Tares tools, so it cannot be bound to the project.

Set it up

1. Check that the crew has the project. The command below lists every project handed to the crew, with its progress, builders and repos. Find your dependency upgrades project in it.
2. Open a session with tares factory session. Run it with no argument and it lets you pick a project, or start something new. You can also name the project when you run it.
3. Pick the dependency upgrades project. The session sees that the crew has it and asks whether to take it over. Say yes.
4. Wait a moment while the builders push their work and write their progress. Your session then reads from their branches and pull requests.
5. Finish the remaining upgrade tickets in the session, on the branches and pull requests the crew left.

tares factory projects
tares factory session

If you want to close the project out yourself, tares factory finish marks a project done. You give it the project and a few words saying why.

If the crew is not running yet, the one command that brings it up is tares factory crew up. The full order for a new setup, including the MCP endpoint, is on Get started. Run tares factory doctor at any point to check everything the crew needs.

What you get

• No restart. You continue from the existing branches and pull requests instead of redoing the upgrades.
• A clean handoff. The crew stops and writes its progress first, so you are not working alongside builders that keep pushing to the same branches.
• Context that stays. The plan, tickets, reviews and the crew’s recorded assumptions are on Tares, and your session works against them.
• Your own pace. You work in a normal Claude Code session, with your AGENTS.md and memory, and no longer wait on the crew’s questions for this project.
• Your choice. Say no at the prompt and the crew keeps going.

When something else fits

• If you only need to answer a question or give a decision, stay in the orchestrator with tares factory crew attach and let the crew finish. It is the one session that brings you what needs you.
• If you want everything to stop for a while without taking the work yourself, tares factory crew halt stops merges, pushes and new sessions until tares factory crew resume.
• If the project is small, build it from the start in your own session instead of handing it to the crew.

Related