Guides

Pick up a teammate's session

Hand off a session: pick up a teammate's work as your own fork, or continue your session in another harness without losing context.

Last updated November 15, 2026View as Markdown

Work moves between people and harnesses. EasyCode has two ways to hand off a session, and neither loses the context:

  • Pick up: continue a teammate's session (or your own from another computer) on your machine. You get a new session, a fork with its history, and theirs stays as it was.
  • Continue in…: move your own session to another harness, say from Claude Code to Codex when a plan runs out. The session stays the same; only the harness changes.

Pick up a teammate's session

Desktop app

Picking up runs on your machine, so it needs the desktop app, signed in to your org. In the web app, a session's page shows Open in desktop, which opens the same session there.

Org sessions sync to your team, so a teammate's work shows in Sessions under Team. This machine lists the sessions your own computer holds.

Open the session

Open it from Sessions, or from your inbox when a teammate assigned it to you with Assign. If the session is private, or its content isn't shared, you see "Ask" and their name in place of the button: ask them to share it.

Press Pick up

The Pick up dialog reads the session and shows what would happen. Nothing starts yet.

  • Harness and Account: where it continues. It starts on the session's own harness when yours is ready.
  • Continue in: the folder on this machine that holds the repo. If you have no clone, it says so and links to Repos, where you clone it; then press Retry.
  • How it continues: Resume natively when the same harness can resume the transcript, else Start from a brief, with the reasons. A different harness, an older harness version, or history only the writer's account can read all mean a brief.
  • Changes: the files from your teammate's changes that will be applied.

Check the held-back files

Files that run code or configure the agent are held back under Changes that run code or configure the agent. The changes apply without them unless you tick Include them and confirm a second time.

Pick up

Press Pick up. EasyCode downloads the session and applies its changes in a fresh worktree of your clone, at the commit the work started from. Your own checkout and branch are untouched. The new session opens with a pick-up note as its first message, and it records where it came from.

If a file in your clone conflicts, nothing is created and the dialog lists the conflicting files. If the session is already live on this machine, you see Open live session instead.

Your org admin can pause pick-ups with the pickup switch; the dialog then says so. Sessions reach the team only while sync is on.

Hand off your session to another harness

Use this when a harness's plan hits its limit, or another harness suits the next step better. It works on a Chat session.

Open Continue in…

In the session, open More actions and choose Continue in…. When a plan's limit is reached, the banner ("Limit reached · resets …") offers Continue in… too, with only the harnesses and accounts that still have room.

Choose the target

Pick the Harness, and the Account if it has more than one. Model is optional. Budget caps the brief, from 4,000 to 64,000 tokens; the default comes from handoff.budgetTokens.

Write a summary adds a summary of the work so far. It runs one forked turn on the current harness; the session's own thread is untouched. Its default is handoff.summary.

Preview and edit the brief

Press Preview. The brief is built from the session's record: the goal, the summary, files changed, commits, to-dos, an open question, recent turns and where the log is. A table shows each section's tokens, and Dropped to fit lists what was cut. Edit the brief in the box if you want.

Continues as says how it lands: the harness's own transcript, the harness's importer, a new thread from the brief, or, if this harness had the session before, its earlier thread with what changed since.

Continue

Press Continue in and the harness name. The session waits, idle, on the new harness for your next message.

Some things never carry over: tool calls come across as text, thinking doesn't come across, and the prompt cache starts cold. The new harness can read the full history at any time with the session_read tool.

You can't hand off while a turn is running. Wait for it to end, or interrupt it. If the session moves on after a preview, preview again.

Something wrong or missing? Suggest a change

On this page