1
00:00:00,120 --> 00:00:03,630
Running Codex on your phone used to feel
like watching a soccer match through a

2
00:00:03,680 --> 00:00:05,140
keyhole, you know?

3
00:00:05,200 --> 00:00:09,320
You could- you could see the ball move,
but good luck directing the play.

4
00:00:09,360 --> 00:00:16,360
But with this iOS 1.2026.181 release, it-
it really shifts

5
00:00:16,400 --> 00:00:20,900
from this passive log viewer where you're
just squinting at terminal outputs,

6
00:00:21,380 --> 00:00:26,460
to actually having active,
conversation-driven task control right in your hand.

7
00:00:27,080 --> 00:00:31,610
I mean, they've completely redesigned how
we interact with the agent's workspace on

8
00:00:31,640 --> 00:00:32,380
a small screen.

9
00:00:37,212 --> 00:00:38,502
Yeah, I remember trying to read a
three-hundred-line build failure on my phone last

10
00:00:38,542 --> 00:00:40,802
month and just giving up.

11
00:00:40,822 --> 00:00:45,122
But now, they've brought in proper branch
comparisons and change filters.

12
00:00:45,672 --> 00:00:50,562
So instead of scrolling endlessly, you can
actually filter the diffs by staged,

13
00:00:50,702 --> 00:00:55,362
unstaged, branch, or- or even just the
changes made in the last turn of the chat.

14
00:00:55,962 --> 00:01:00,462
That last-turn filter is honestly a
lifesaver when you're walking and just need to

15
00:01:00,482 --> 00:01:03,992
know, okay, what did the agent just modify
in that last prompt?

16
00:01:04,874 --> 00:01:10,634
Exactly, and the UI for comparing branches
is surprisingly dense but usable.

17
00:01:10,674 --> 00:01:15,534
You're not looking at a- a massive
side-by-side git diff that gets squished into a

18
00:01:15,594 --> 00:01:17,174
ten-pixel column.

19
00:01:17,214 --> 00:01:22,704
It's using a single-column, line-by-line
unified diff format where you can tap to

20
00:01:22,794 --> 00:01:23,654
expand files.

21
00:01:24,414 --> 00:01:28,724
And they've added this smart touch target
system so you aren't constantly

22
00:01:28,754 --> 00:01:33,034
fat-fingering the wrong line of code when
you're trying to stage or discard a

23
00:01:33,074 --> 00:01:33,474
change.

24
00:01:34,424 --> 00:01:37,714
It- it feels like they actually tested
this on a bumpy subway ride.

25
00:01:38,564 --> 00:01:39,414
Oh, absolutely.

26
00:01:39,734 --> 00:01:43,664
The testing was probably done by
developers desperate to close a ticket on their

27
00:01:43,694 --> 00:01:44,054
commute.

28
00:01:44,694 --> 00:01:49,174
And you can actually manage the lifecycle
of these tasks directly from the thread

29
00:01:49,214 --> 00:01:49,374
now.

30
00:01:49,914 --> 00:01:54,554
You can fork a task, open an existing one,
or search through your task history

31
00:01:54,594 --> 00:01:56,954
without leaving the chat interface.

32
00:01:56,994 --> 00:02:01,354
Plus, they've put the runtime credit
tracking right there in the updated task menu.

33
00:02:01,814 --> 00:02:05,774
So you see exactly how many credits a run
is burning in real time,

34
00:02:06,154 --> 00:02:10,094
which is- well, it's pretty crucial when
you're running heavy build steps in a

35
00:02:10,153 --> 00:02:13,014
sandbox and don't want to wake up to a
surprise bill.

36
00:02:13,797 --> 00:02:16,517
Right, because those sandbox runtimes
aren't free.

37
00:02:17,077 --> 00:02:22,527
And speaking of sandboxes, the way they've
streamlined SSH connections is- is pretty

38
00:02:22,617 --> 00:02:27,097
clever, but it definitely comes with some
security caveats we should talk about.

39
00:02:27,687 --> 00:02:33,097
They've added this new quick SSH shortcut
where you can paste a private key directly

40
00:02:33,237 --> 00:02:37,877
into the app, or use a credential-free
link to pair your phone with a running cloud

41
00:02:37,897 --> 00:02:38,407
workspace.

42
00:02:39,057 --> 00:02:42,707
It's incredibly fast to get a terminal
session going, but, uh,

43
00:02:42,957 --> 00:02:47,097
pasting a raw SSH private key into a
mobile app container...

44
00:02:48,477 --> 00:02:50,297
man, that makes my stomach turn a bit.

45
00:02:51,676 --> 00:02:55,126
Yeah, I- I- I definitely winced when I
first saw that text box.

46
00:02:55,666 --> 00:02:58,926
If you're doing that, you really need to
be using ephemeral,

47
00:02:59,166 --> 00:03:05,246
single-session keys created specifically
for that sandbox, not your main master key.

48
00:03:05,306 --> 00:03:10,066
But if you handle the keys cleanly, the
actual workflow once you're in is super

49
00:03:10,106 --> 00:03:10,406
slick.

50
00:03:10,956 --> 00:03:15,566
They've added inline attachment previews
in the terminal and you can actually tap

51
00:03:15,626 --> 00:03:20,506
text inside a command transcript or build
log to inject it straight into your

52
00:03:20,546 --> 00:03:21,606
composer.

53
00:03:21,626 --> 00:03:25,816
So if a build fails, you don't have to try
and highlight a messy stack trace with

54
00:03:25,846 --> 00:03:30,786
those annoying iOS text selection
handles--you just tap the block and it's ready to

55
00:03:30,826 --> 00:03:32,486
go in your next prompt.

56
00:03:32,502 --> 00:03:35,922
Which is huge, because otherwise you're
spending three minutes just trying to

57
00:03:36,002 --> 00:03:37,442
copy-paste an error code.

58
00:03:38,062 --> 00:03:41,822
And this also plays into how you handle
those "Needs input" halts.

59
00:03:42,582 --> 00:03:46,782
If the agent gets stuck because it needs a
manual confirmation or a password,

60
00:03:47,302 --> 00:03:50,022
and you don't have a local terminal handy
to bash through it,

61
00:03:50,622 --> 00:03:53,462
you can use the workspace recovery
feature.

62
00:03:53,542 --> 00:03:58,202
It- it basically lets you take control of
the active shell session directly through

63
00:03:58,262 --> 00:04:03,222
the chat interface, respond to the prompt,
and then hand control back to the agent.

64
00:04:03,862 --> 00:04:08,722
It's a really elegant way to handle those
little operational roadblocks that used to

65
00:04:08,762 --> 00:04:10,562
completely kill a mobile run.

66
00:04:11,654 --> 00:04:13,924
It really keeps the momentum going.

67
00:04:14,004 --> 00:04:18,383
Oh, and before we wrap up, we should
mention some of the smaller quality-of-life

68
00:04:18,464 --> 00:04:21,904
tweaks they snuck into 1.2026.181.

69
00:04:22,604 --> 00:04:27,584
They finally fixed that annoying issue
where you'd get signed out and lose all your

70
00:04:27,664 --> 00:04:31,644
active terminal connection states--now
they persist across sessions.

71
00:04:32,324 --> 00:04:37,004
Plus, they fixed a nasty deadlock issue
that was freezing the chat UI when you tried

72
00:04:37,024 --> 00:04:41,884
to load large diffs, and the code
autocomplete inside the mobile composer actually

73
00:04:41,944 --> 00:04:43,044
feels snappy now.

74
00:04:43,584 --> 00:04:46,684
It's just a bunch of small, really solid
engineering wins.

75
00:04:48,242 --> 00:04:51,482
Yeah, no more app restarts just because a
diff was too big.

76
00:04:52,242 --> 00:04:55,282
Alright, that's a quick look at the new
Codex iOS update.

77
00:04:55,722 --> 00:04:56,522
Catch you next time.

78
00:04:57,149 --> 00:04:57,988
See ya.