Can I take over docs updates 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. Run tares factory session and say yes when it asks whether to take the project over. The crew stops, its builders push what they have, and your session continues from their branches and pull requests.
How it works
A docs updates project that the crew is working on is a project like any other. Tares keeps its plan, tickets, reviews and your earlier answers, so your session starts from the full record instead of from scratch.
When you open a session on a project the crew has, it asks whether to take it over:
- Yes: the crew stops. Its builders push what they have and write down their progress. Your session then carries on from their branches and pull requests.
- No: the crew keeps the project and you change nothing.
The session is a Claude Code session started by Tares, with the Tares plugin and bound to the project. Your shared AGENTS.md and memory apply, and the record of the session lands on the project. A plain claude has no Tares tools, so start the session with tares factory session rather than opening Claude Code yourself.
The session works the project’s tickets, so the unfinished docs tickets stay the unit of work. If the tickets live in Linear or GitHub Issues, they stay there. Tares reads them about once a minute and sessions change them with their own tools. Tares never writes to them.
Set it up
-
Make sure Tares is reachable. On a local Tares, keep
tares uprunning and, in a second terminal, keep the MCP endpoint running, since every session reaches Tares through it. On Tares Cloud, sign in withtares login. -
Check that Claude Code is signed in and that
ghis signed in with write access to the repos involved, so your session can push to the crew’s branches and work on its pull requests. -
List the projects the crew has and find the docs updates project, with its progress, builders and repos:
tares factory projects -
Open your own session on it. With no argument the command lets you pick a project, so choose the docs updates one:
tares factory session -
When the session asks whether to take the project over, say yes. The crew stops and its builders write their progress.
-
Let the session read the progress and continue. It carries on from the branches and pull requests the crew left, so you review and extend that work instead of redoing it.
-
When the docs are done, finish the work through your session. If you want to close the project yourself,
tares factory finishmarks a project done with your own words.
If something does not work, run tares factory doctor to check everything the crew and its sessions need. Get started has the full setup, the commands table and the details of each step.
What you get
- A clean hand-over. The crew stops pushing and merging on the project, so you and the crew do not edit the same branches at once.
- No lost work. Builders push what they have and write their progress before they stop, and the branches and pull requests stay where they were.
- Context kept. The plan, tickets, reviews, assumptions and your earlier answers stay on Tares, and your session sees them.
- Your own pace. You finish the docs updates in a normal Claude Code session, with your own prompts, instead of waiting for questions to come to you through the orchestrator.
- A record. The session’s record lands on the project, so the history shows where the crew stopped and where you picked up.
- A way to opt out. Answer no to the take-over question and the crew keeps the project untouched.
When something else fits
- If you only want to steer the project, stay with the crew. Run
tares factory crew attach orchestrator, answer its questions one at a time, and let it keep building and merging. - If you want to pause merges and pushes without taking the project over, run
tares factory crew haltwith a reason.tares factory crew statusandtares factory crew deskshow where the crew stands and what waits for you.