Continue a teammate's work

A teammate is out for the day and left a branch half done. Their session has the context you would otherwise ask them for: what they tried, what they rejected, what is left. It does not matter which coding agent they used or which one you use; the example below has Dana in Claude Code and you in Cursor

Dana's session is stored as she works in Claude Code; when she is out, you recap it in Cursor and finish the feature. Everything below stands on its own

1. Find the session

If your teammate’s default audience is the organisation, or the repository is in a project you both belong to, the session is already yours to read: open Sessions, set Scope to the repository, and pick it from the list, or ask your agent to find it by describing the work

If it is private, the owner shares it from the web app: open the session, choose Share, pick Teams & people, add you, then Apply. Ask them for exactly that; a link on its own grants nothing, so a link to a private session shows “not available” until it is shared

2. You pick it up

Check out the branch, start your agent in the repository, and ask:

Recap session acme-billing-rate-limit. What was decided, what is done, and what is left? Then continue from the next task

Or, if you do not know the session:

What has the team been doing on rate limiting this week? Find the sessions and summarise where they stopped

The agent cites the sessions it found, so you can open any of them in the web app to read the actual turn

3. Loose ends come with it

If your teammate stopped short and said so, the agent recorded a loose end: a concrete piece of unfinished work. Ask:

What loose ends did that session leave? Claim the first one and work on it

Claiming it marks the loose end as yours, so a third person does not duplicate the work. Close it when it is done, or release it if you cannot finish

4. The plan carries on

The plan your teammate declared is attached to your session now. Their Overview and yours show the same task list, and the work item, if the session was filed on a ticket, shows both sessions under it

Troubleshooting

“That session isn’t available”: it was not shared with you. Ask the owner to share it with you from the session’s Share control
Two people pick up the same loose end: whoever claimed it first owns it; the second claim is refused and says who has it