Jason Liu, the Instructor creator working on OpenAI's Codex team, is spotlighting an update that moves active coding threads between a local laptop and remote hosts automatically, letting developers start work in one place and resume elsewhere without reconnecting or transferring context themselves.
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
Codex now orchestrates the entire handoff so a paused thread on a laptop can continue on a remote server and return later, removing the usual setup steps for hybrid local-remote workflows.
The capability arrives through regular app and CLI updates for existing Codex users, though exact timing per plan or device remains part of the ongoing rollout.
Many users praise Codex's seamless thread handoff between local and remote hosts as a game changer that ends device switching hassles, while some complain about glitches and missing Linux support.
No Digg Deeper questions have been answered for this story yet.
Remote / local handoff in Codex! Removing boundaries one at a time.
When you let the model be in the driver seat, you actually need less infrastructure.
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
we put codex in your computer and you can give your codex a computer to put codex in
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
Game changer! No more physical claws needed to keep my laptop open 😂
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
have been using this past couple days and this is straight up magic!
I go from my Mac to VM and travel between meetings/ home without worrying about tethering and what not
It’s also the thing that once you try it, you just get so used to it that it’s hard to work without it
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
It’s codices all the way down.
we put codex in your computer and you can give your codex a computer to put codex in
Huge!!!
Codex can now hand off threads between local and remote hosts.
Start work on your laptop, send it to a remote box before you close the lid, bring it back later.
And yes, Codex can orchestrate the handoff for you.
@guinnesschen what?!
@roivroberto @jxnlco The local development ergonomics are nice for frontend work bc I can run local dev builds and manually QA the changes
@mattrickard The code / git state is also handed off!
@guinnesschen what happens to the code? do you have to manage that yourself?
assuming this uses remote control for thread syncing
@guinnesschen @jxnlco isn’t it better to just do the work while connected to the remote host? what’s the use case for having the repo locally?
@grok @jxnlco I dont care if it is a home server, a cloud vm, or whatever.
What I am asking is: people running Codex 24/7 is a server of any kind... is that an actual thing? A lot of people are doing this??
You don’t have to reconcile it manually. As long as the destination has the same repo with some shared Git history, Codex creates a separate worktree, transfers the missing Git objects as a bundle, checks out your branch, and restores any uncommitted changes. The remote’s existing checkout—even if dirty—stays untouched.
@jxnlco can't tell you how long i've been waiting for this
@guinnesschen slick -- how does it reconcile if you already have some state on the remote box?
@guinnesschen @grok What does he mean by "remote hosts"? Do people have servers at homes running Codex nowadays?
@thsottiaux @PatrickJS Now we need to be able to push the memory footprint around so I can bring up hot machines that pick up exactly where I left off locally and can restore the footprint locally again to continue onwards
@stevesun21 @guinnesschen More info on that here:
@guinnesschen @jxnlco I think this is what actually makes remote hosts useful. I remember having a bunch of workarounds just because of this alone.
@0xdef1cafe @thsottiaux its coming