Handing a half-done branch to a teammate

Small teamsTeam where someone goes on leave

Meera started a payments refactor and went on leave halfway through. Kabir took over the branch and had to work out what was finished from commit messages.

How do I find out what's finished on a half-done branch from a teammate who went on leave?

With ArcRoom, the first person's agent records each finished step with complete_task, and split_task keeps the parts. The new owner's agent asks find_task for the work, such as 'payments refactor', and gets the parts: which are done and which aren't. It then continues with the open parts. Steps the first agent never recorded are invisible.

Also asked as: I took over a teammate's branch and can't tell what's done. What do I do? · How do I hand a half-finished task from one developer's AI agent to another? · Can an AI agent see which steps of a refactor are already complete?

The work

Meera's agent recorded each finished step through complete_task, and split_task kept the parts.

ArcRoom keeps
  • Reused answer
  • Saved answer
  • Split into parts
The next agent gets

split_task → payments refactor

Step by step

  1. Meera's agent recorded each finished step through complete_task, and split_task kept the parts.
  2. Kabir's agent asks find_task for 'payments refactor' and gets the parts, which are done and which aren't.
  3. It continues with the open parts.

What the agent sees

split_task → payments refactor
✓ move fees to ledger table (meera)
✓ new PaymentIntent wrapper (meera)
○ migrate old invoices
○ remove legacy charge()

Compared with today's tools

Handover note in the PR

Meera writes done, not done and gotchas in the PR description, and Kabir pastes it into his agent.

Setup
0 min
Ongoing
30–60 min to write a good note before leave

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per person (npx arcroom init)
Ongoing
None

A careful human note can beat ArcRoom; ArcRoom still has the answers and decisions when the note is rushed or never written.

Where it stops

Steps the first agent never recorded are invisible. The last-run note shows your own last session first, then a teammate's on the same project.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in small teams