Codex Handoff: Move a chat and working files between Macs

Why it matters

Handoff can reduce the Git and setup work required to switch machines, but developers still need a precise contract for files, secrets and failed transfers.

Developing Adventures (@DevAdventur3s) demonstrated Codex moving a coding chat and its project state from one Mac to another on September 13th, including an untracked file that arrived with the same hash. The test used a modified Codex build with feature flags enabled, so it was a close look at an existing Handoff workflow rather than a new OpenAI release.

https://x.com/DevAdventur3s/status/2099267363107410128

The 13-post thread showed two paths: sending work from a local machine to the cloud, and transferring it to another Mac. In the Mac-to-Mac test, the conversation continued on the destination machine and the untracked file moved without a Git commit or push.

That last detail matters because conversation continuity alone is already common across agent interfaces. Carrying the working state means a developer can leave a laptop, continue on a Mac mini or another workstation, and avoid packaging unfinished changes merely to change machines.

The test was narrow. Developing Adventures verified one untracked file and matching file hashes, while explicitly stopping short of claiming that every local asset transfers. Ignored files, repositories with a large mix of staged and unstaged edits, secrets, environment variables and recovery after a failed transfer were not tested.

Handoff predates the demo

OpenAI added remote task Handoff in its June 18th changelog. The release allowed users to move a thread to a matching project on a connected host and continue it there. OpenAI's current remote connections documentation describes Handoff as moving an existing chat and its Git state between a local computer and a connected remote host.

The destination must already contain a saved project for the same Git repository. Codex creates or reuses a worktree there, transfers the chat and Git state, and changes the thread's run location. If Codex is producing a response when the user starts the transfer, Handoff interrupts that response before moving the thread.

Those constraints make Handoff closer to a managed relocation of a development session than live process migration. Developing Adventures made the same distinction in replies to the demo: the test moved conversation state and files, rather than a running process. It did not establish whether an agent can resume in the middle of a command, recover a partially completed tool call, or recreate credentials and environment settings on another machine.

OpenAI's current documentation also separates host-to-host Handoff from Codex cloud. The host transfer flow does not support a Codex cloud environment as its destination. Local-to-cloud delegation has existed separately: OpenAI documented the ability to send tasks from the IDE to Codex web and later apply the resulting changes locally in September 2025.

That distinction was blurred in the initial demo, which grouped cloud and Mac-to-Mac movement under Handoff. Developing Adventures later clarified that cloud Handoff already existed and that the useful part of this test was transferring the task and files to another Mac.

The missing contract is the file boundary

The practical question is which parts of a developer's workspace Codex treats as portable state. OpenAI's documentation promises transfer of the chat and Git state, but it does not present Handoff as a complete clone of the source machine. The destination still supplies its own installed dependencies, credentials, permissions, tools and machine configuration.

An unchanged hash on one untracked file is evidence that Handoff can carry work that has never entered Git. It does not define the exclusions. Developers will need predictable behavior around .gitignore, large generated files, local databases, build artifacts and credential files before treating Handoff as a routine way to move sensitive or complicated work.

The appeal remains straightforward. Coding agents increasingly run tasks long enough to outlast a commute, a battery or the machine where the work began. OpenAI has spent 2026 extending Codex across desktop, mobile, remote hosts and cloud environments. In July, OpenAI merged the standalone Codex app into the ChatGPT desktop app, while keeping Codex projects and remote access inside the combined product.

Developing Adventures also said Codex produced the demonstration itself, controlling recording through the creator's Halo MCP tool, then editing the footage and adding music under human direction. That claim is separate from the Handoff test, but it captures where OpenAI is taking the product: the coding thread is becoming a portable workspace for longer jobs, rather than a chat box attached to one computer.