1
00:00:00,359 --> 00:00:05,960
So I spent my entire morning commute
kicking off a full Rust compile from my phone,

2
00:00:06,460 --> 00:00:09,800
and for once, the app didn't just crash in
my pocket.

3
00:00:10,224 --> 00:00:14,525
Wait, you, you actually ran a full cargo
build on mobile while walking to the train?

4
00:00:14,905 --> 00:00:15,584
I did!

5
00:00:16,044 --> 00:00:21,484
And before we get into how that actually
worked, a huge thank you to Jellypod for

6
00:00:21,545 --> 00:00:24,764
sponsoring the podcast and making this
daily show possible.

7
00:00:25,484 --> 00:00:29,264
But yeah, Ethan, ChatGPT for iOS version

8
00:00:29,604 --> 00:00:36,284
1.2026.244 rolled out some massive updates
for remote development.

9
00:00:36,542 --> 00:00:39,822
Yeah, the big piece here is the new
worktree creation picker.

10
00:00:39,950 --> 00:00:44,622
When you start a remote Codex session from
your phone, you don't just get dumped

11
00:00:44,686 --> 00:00:47,902
onto whatever stale main branch is sitting
on your host machine.

12
00:00:48,042 --> 00:00:53,182
The release notes explicitly say you can
choose a starting branch for new worktrees,

13
00:00:53,235 --> 00:00:55,182
or include your current local changes.

14
00:00:55,566 --> 00:00:56,886
Which is huge!

15
00:00:57,326 --> 00:01:01,107
Because previously, if you were mid
thought at your desk, stepped away to get

16
00:01:01,167 --> 00:01:05,507
coffee, and wanted to keep working from
your phone, those uncommitted edits on your

17
00:01:05,526 --> 00:01:08,306
desktop were essentially locked away.

18
00:01:08,446 --> 00:01:13,306
Now, you just bundle those uncommitted
local changes directly into the new remote

19
00:01:13,366 --> 00:01:13,726
session.

20
00:01:14,125 --> 00:01:18,525
Mm, okay, but let's talk about what
happens when you actually press go on that

21
00:01:18,571 --> 00:01:19,405
mobile prompt.

22
00:01:19,535 --> 00:01:26,405
Usually, setup scripts like pnpm install
or cargo build take two or three minutes.

23
00:01:26,525 --> 00:01:31,325
On older iOS versions, the second you put
your phone back in your pocket,

24
00:01:31,465 --> 00:01:36,925
iOS background execution would suspend the
app, kill the WebSocket connection,

25
00:01:36,965 --> 00:01:38,845
and your setup task would fail.

26
00:01:39,292 --> 00:01:45,212
Right, but on iOS 26, they are leveraging
Live Activities and a persistent

27
00:01:45,253 --> 00:01:46,092
background daemon.

28
00:01:46,652 --> 00:01:51,892
So worktree initialization, repository
cloning, and those long dependency installs

29
00:01:52,152 --> 00:01:53,612
keep running in the background.

30
00:01:54,112 --> 00:01:57,093
You get real time progress updates right
on your lock screen,

31
00:01:57,433 --> 00:01:59,052
no stalling, no timeouts.

32
00:01:59,412 --> 00:02:01,912
It's slick, I admit the UX is clean.

33
00:02:02,573 --> 00:02:07,753
But, um, Maya, from a software quality
perspective, doesn't it make you nervous to

34
00:02:07,772 --> 00:02:13,713
dump dirty, unvetted local working tree
diffs straight into an automated agent

35
00:02:13,772 --> 00:02:14,253
environment?

36
00:02:14,671 --> 00:02:16,152
Why would it make me nervous?

37
00:02:16,451 --> 00:02:18,811
It's literally what I was working on five
minutes ago.

38
00:02:19,167 --> 00:02:24,207
Because you might have half baked debug
statements, temporary environment variables,

39
00:02:24,260 --> 00:02:26,687
or broken logic sitting in your workspace.

40
00:02:26,900 --> 00:02:32,287
If the agent takes that dirty state as
ground truth and starts layering automated

41
00:02:32,347 --> 00:02:37,727
commits on top of it, you're looking at
messy merge conflicts or security leaks when

42
00:02:37,775 --> 00:02:40,047
that worktree tries to sync back to main.

43
00:02:40,548 --> 00:02:43,067
I see your point on security hygiene,
sure.

44
00:02:43,647 --> 00:02:47,427
But as a practical matter when you're
testing an idea on the go,

45
00:02:48,047 --> 00:02:52,088
avoiding the friction of having to stash,
push to a remote branch,

46
00:02:52,128 --> 00:02:54,267
and re-fetch just to use your phone?

47
00:02:54,887 --> 00:02:58,027
That speed win is worth the risk for most
devs.

48
00:02:58,292 --> 00:03:02,772
Well, speaking of speed wins on mobile,
the prompt composer got a really interesting

49
00:03:02,829 --> 00:03:04,212
update in this release too.

50
00:03:04,324 --> 00:03:09,092
They added in composer at mentions for
Codex cross task references.

51
00:03:09,302 --> 00:03:10,443
Oh, I saw that!

52
00:03:10,823 --> 00:03:15,342
You type the at symbol in the prompt
composer, and it pops up an auto complete list

53
00:03:15,402 --> 00:03:18,363
of your active and archived Codex task
IDs.

54
00:03:18,902 --> 00:03:24,602
So if subagent A was refactoring a
database schema, you can at mention subagent A's

55
00:03:24,682 --> 00:03:29,882
task ID inside subagent B's prompt, and it
pulls in that context automatically.

56
00:03:30,208 --> 00:03:34,848
Yeah, no more manually switching screens
to copy and paste session transcripts.

57
00:03:34,928 --> 00:03:39,888
And alongside that, they fixed a massive
friction point with draft preservation.

58
00:03:40,004 --> 00:03:45,088
Previously, if an agent stopped to ask you
a clarification question while you were

59
00:03:45,145 --> 00:03:50,048
typing a multi step follow up prompt,
answering the question would wipe out your in

60
00:03:50,110 --> 00:03:52,368
progress draft in the composer.

61
00:03:52,674 --> 00:03:54,934
Oh, that used to drive me crazy!

62
00:03:55,375 --> 00:04:00,194
You'd lose three paragraphs of complex
instructions just because you tapped yes to

63
00:04:00,274 --> 00:04:01,215
approve a tool call.

64
00:04:01,875 --> 00:04:07,034
Now those responses are completely non
blocking, so your draft stays safe while the

65
00:04:07,134 --> 00:04:07,954
agent keeps running.

66
00:04:08,250 --> 00:04:08,890
Right.

67
00:04:08,924 --> 00:04:11,930
Though we should mention a couple of
technical caveats here.

68
00:04:12,074 --> 00:04:14,810
That remote worktree feature we talked
about?

69
00:04:15,050 --> 00:04:20,730
It requires your host machine to be
running an active daemon with Codex CLI version

70
00:04:20,810 --> 00:04:23,210
0.153 or higher.

71
00:04:23,477 --> 00:04:29,050
If your local CLI is outdated, the mobile
client just won't see the worktree picker.

72
00:04:29,322 --> 00:04:35,281
And under the hood, those dirty state
transfers actually rely on temporary Git stash

73
00:04:35,341 --> 00:04:35,821
patches.

74
00:04:36,341 --> 00:04:41,621
So if your host branch diverges or changes
on the desktop while the mobile agent is

75
00:04:41,681 --> 00:04:45,941
running against that stash patch, you will
hit merge conflicts when the session

76
00:04:45,982 --> 00:04:46,501
completes.

77
00:04:46,792 --> 00:04:47,792
Exactly.

78
00:04:47,859 --> 00:04:49,672
It's not magic, it's Git.

79
00:04:49,832 --> 00:04:55,432
But overall, between these draft fixes, at
mentions, and Voice mode finally

80
00:04:55,483 --> 00:05:00,232
respecting configured model defaults and
reasoning effort settings strictly,

81
00:05:00,278 --> 00:05:03,112
mobile code reviews feel way more viable
now.

82
00:05:03,256 --> 00:05:07,992
They even added back history and
remembered reading positions for multi file

83
00:05:08,062 --> 00:05:08,632
reviews.

84
00:05:08,884 --> 00:05:13,164
It definitely feels like mobile is turning
into a first class workflow instead of

85
00:05:13,204 --> 00:05:13,804
just a gimmick.

86
00:05:14,525 --> 00:05:16,224
Alright, that's our quick take for today.

87
00:05:16,724 --> 00:05:20,385
Thanks again to Jellypod for making this
episode possible, and we'll see you all

88
00:05:20,444 --> 00:05:20,784
tomorrow!

89
00:05:21,167 --> 00:05:22,207
Take care, everyone.