Hand a coding-agent task to a teammate without starting over

A teammate agrees to pick up your agent task while you are out. You send the branch and the thread link. Ten minutes later they ask which commit was green, what still fails and what they should do next.

The branch holds the patch, but the person taking over needs the reasoning behind it and a reliable starting point. A useful handover lets them verify the state without replaying the whole conversation.

Make the task accessible

If the work lives only in a local coding session, push it to an accessible branch and prepare a readable summary. With Hoplite cloud agents, the CLI handoff can create a cloud thread from an active local Claude Code, Codex or OpenCode session. It transfers user and assistant conversation, not tool outputs, hidden reasoning, ignored files, unpushed changes or running processes. By default uncommitted changes and unpushed commits stay local and trigger a warning. Use hoplite handoff --autopush to commit and push the branch before the thread starts.

Check what the handoff leaves out before sending the thread link. A conclusion such as "the second approach passed" needs the test command, the result and the commit you ran it on.

In Hoplite, workspace membership is managed under Settings, Workspace, Members. Invite the teammate normally and confirm they can access the repository for the task. A link alone does not grant access.

Leave a note with the current decision

Use the thread's /note command to pin the information someone needs first. Hoplite describes notes as shared context in its thread management guide.

For a hypothetical upload bug, a useful note could read:

The branch fixes upload retries after interrupts. Unit tests pass at the latest pushed commit. Large-file browser check is still open. Keep the retry limit, the mobile client needs it. Open: separate paused UI state or not. Finish verification, then request review from the upload owner. Do not merge before that review.

Explain any unsuccessful approach that affects the next decision. You do not need to list every edit. The teammate needs to know which path wastes time or repeats a known failure.

When you cite test results, include the command and the commit in the handover. If the result depends on a local-only fixture, share a safe, reproducible fixture before you hand over the task.

Use the thread and PR as a shared record

A teammate who opens another member's cloud thread can choose Add to my threads to follow it under My threads. This follows the conversation without posting a message. It does not take over a live terminal session.

To give them a concrete place to continue, open a draft PR with the current work. Hoplite links PRs to their originating threads and supports starting a new thread from an existing PR's head branch. The teammate can select the repository, choose PRs in the source picker and start with the PR metadata available as context.

Authorized workspace members with repository access can also request work through a PR comment using @usehoplite. This only works for head branches in the same repository. Fork PRs are rejected.

Choose one continuation path and write down who owns it. Stop the previous agent and wait until it has fully stopped before another run edits the same branch. A shared branch with two independent writers needs coordination even when everyone has the right permissions.

Ask the recipient to verify before changing code

First, they should inspect the branch and reproduce the last known result. For the upload example, the teammate should confirm the current commit, run the unit test named in the note and inspect the remaining browser case.

If the baseline differs, investigate before adding more changes. The original environment may have hidden dependencies or the branch may have moved after the note was written.

Hoplite can export a readable Markdown transcript from the thread's action menu. The Messages export contains prompts and replies only, so include necessary test evidence separately when the handover happens outside the app. Choose Messages + activity or Full if the recipient needs tool activity.

Try the process with one unfinished task at the end of a working day. Leave the pushed branch, draft PR, thread link and next decision in one place. Ask your teammate to continue from that record, then improve the note based on the questions they still asked.