iOS Remote Worktrees and Smarter Mobile Codex

Maya

So I spent my entire morning commute kicking off a full Rust compile from my phone, and for once, the app didn't just crash in my pocket.

Ethan Park

Wait, you, you actually ran a full cargo build on mobile while walking to the train?

Maya

I did! And before we get into how that actually worked, a huge thank you to Jellypod for sponsoring the podcast and making this daily show possible. But yeah, Ethan, ChatGPT for iOS version 1.2026.244 rolled out some massive updates for remote development.

Ethan Park

Yeah, the big piece here is the new worktree creation picker. When you start a remote Codex session from your phone, you don't just get dumped onto whatever stale main branch is sitting on your host machine. The release notes explicitly say you can choose a starting branch for new worktrees, or include your current local changes.

Maya

Which is huge! Because previously, if you were mid thought at your desk, stepped away to get coffee, and wanted to keep working from your phone, those uncommitted edits on your desktop were essentially locked away. Now, you just bundle those uncommitted local changes directly into the new remote session.

Ethan Park

Mm, okay, but let's talk about what happens when you actually press go on that mobile prompt. Usually, setup scripts like pnpm install or cargo build take two or three minutes. On older iOS versions, the second you put your phone back in your pocket, iOS background execution would suspend the app, kill the WebSocket connection, and your setup task would fail.

Maya

Right, but on iOS 26, they are leveraging Live Activities and a persistent background daemon. So worktree initialization, repository cloning, and those long dependency installs keep running in the background. You get real time progress updates right on your lock screen, no stalling, no timeouts.

Ethan Park

It's slick, I admit the UX is clean. But, um, Maya, from a software quality perspective, doesn't it make you nervous to dump dirty, unvetted local working tree diffs straight into an automated agent environment?

Maya

Why would it make me nervous? It's literally what I was working on five minutes ago.

Ethan Park

Because you might have half baked debug statements, temporary environment variables, or broken logic sitting in your workspace. If the agent takes that dirty state as ground truth and starts layering automated commits on top of it, you're looking at messy merge conflicts or security leaks when that worktree tries to sync back to main.

Maya

I see your point on security hygiene, sure. But as a practical matter when you're testing an idea on the go, avoiding the friction of having to stash, push to a remote branch, and re-fetch just to use your phone? That speed win is worth the risk for most devs.

Ethan Park

Well, speaking of speed wins on mobile, the prompt composer got a really interesting update in this release too. They added in composer at mentions for Codex cross task references.

Maya

Oh, I saw that! You type the at symbol in the prompt composer, and it pops up an auto complete list of your active and archived Codex task IDs. So if subagent A was refactoring a database schema, you can at mention subagent A's task ID inside subagent B's prompt, and it pulls in that context automatically.

Ethan Park

Yeah, no more manually switching screens to copy and paste session transcripts. And alongside that, they fixed a massive friction point with draft preservation. Previously, if an agent stopped to ask you a clarification question while you were typing a multi step follow up prompt, answering the question would wipe out your in progress draft in the composer.

Maya

Oh, that used to drive me crazy! You'd lose three paragraphs of complex instructions just because you tapped yes to approve a tool call. Now those responses are completely non blocking, so your draft stays safe while the agent keeps running.

Ethan Park

Right. Though we should mention a couple of technical caveats here. That remote worktree feature we talked about? It requires your host machine to be running an active daemon with Codex CLI version 0.153 or higher. If your local CLI is outdated, the mobile client just won't see the worktree picker.

Maya

And under the hood, those dirty state transfers actually rely on temporary Git stash patches. So if your host branch diverges or changes on the desktop while the mobile agent is running against that stash patch, you will hit merge conflicts when the session completes.

Ethan Park

Exactly. It's not magic, it's Git. But overall, between these draft fixes, at mentions, and Voice mode finally respecting configured model defaults and reasoning effort settings strictly, mobile code reviews feel way more viable now. They even added back history and remembered reading positions for multi file reviews.

Maya

It definitely feels like mobile is turning into a first class workflow instead of just a gimmick. Alright, that's our quick take for today. Thanks again to Jellypod for making this episode possible, and we'll see you all tomorrow!

Ethan Park

Take care, everyone.