Codex adds local-to-remote thread handoff with Git worktree transfer
Codex can now hand off an in-progress thread between local and remote machines and bring it back later. It matters because the handoff carries Git history, branches, and uncommitted changes while leaving the destination checkout untouched.
TL;DR
- guinnesschen's demo showed Codex moving an in-progress thread from a laptop to a remote box, then resuming it later on another machine.
- The handoff carries code state too, because guinnesschen's reply said the code and Git state move with the thread, not just the chat transcript.
- According to guinnesschen's implementation reply, Codex creates a separate worktree on the destination, transfers missing Git objects as a bundle, checks out the branch, and restores uncommitted changes without touching the remote's existing checkout.
- guinnesschen's frontend note and guinnesschen's desktop follow-up framed the split clearly: local is still better for manual QA, while remote can keep making progress from code, tests, and logs.
You can watch guinnesschen's video bounce a session across machines, read guinnesschen's mechanics reply for the Git details, and see dkundel's post note that there is also a UI dropdown for the same handoff flow.
Thread handoff
Codex is adding a literal host-to-host handoff, not just remote control. guinnesschen's demo showed a thread leaving a laptop for a remote machine, while dkundel's post said the same action is exposed in a UI dropdown and can also be triggered in natural language.
The useful bit is continuity. guinnesschen's reply said the code and Git state transfer too, which makes this closer to moving a live working session than reopening a prompt elsewhere.
Git worktree transfer
The implementation detail is the best part of the launch. In guinnesschen's implementation reply, guinnesschen said Codex only needs the destination machine to have the same repo with some shared Git history.
From there, the handoff does four concrete things:
- creates a separate worktree on the destination
- transfers missing Git objects as a bundle
- checks out your branch
- restores uncommitted changes
That same reply adds one more important constraint: the remote machine's existing checkout, even if dirty, stays untouched.
Local QA
The thread around guinnesschen's frontend note makes the intended workflow pretty explicit. Local still wins when you need dev builds, manual QA, or desktop-app testing.
Remote is the keep-going box. guinnesschen's desktop follow-up said it can keep dead reckoning from code, tests, and logs while a laptop is offline, then hand the work back for local verification.
Release edges
The surrounding Codex release cycle still looks a little messy. raunakdoesdev's bug report said build 26.616.30709 broke permissions and outgoing network access, while koltregaskes's mobile complaints listed slow session loads, delayed sends, and draft sync failures between desktop and mobile.
That lands next to a broader mobility push. reach_vb's mobile update list added file browsing, workspace selection, diff controls, MCP approvals, and clearer thread status to Codex Mobile, which makes the new handoff feature look like part of a larger attempt to make sessions portable across surfaces.