1
00:00:00,120 --> 00:00:03,620
So, I was running some heavy, multi-hour
agent loops yesterday,

2
00:00:04,220 --> 00:00:07,410
and my local MacBook was- was basically
melting.

3
00:00:08,100 --> 00:00:11,330
Thanks to Jellypod for helping make this
daily show a reality,

4
00:00:11,880 --> 00:00:16,980
because, uh, otherwise I'd still be
sitting here waiting for my local terminal to

5
00:00:17,020 --> 00:00:17,560
unfreeze.

6
00:00:18,260 --> 00:00:22,440
We finally have a clean way to offload
this entire runtime using the new

7
00:00:22,600 --> 00:00:27,890
DigitalOcean plugin, which lets you
provision persistent remote sandboxes directly

8
00:00:27,920 --> 00:00:28,460
from the chat.

9
00:00:29,202 --> 00:00:31,102
Yeah, I saw the PR for that.

10
00:00:31,622 --> 00:00:36,251
Instead of running node processes or
docker containers locally and watching your

11
00:00:36,422 --> 00:00:41,282
memory footprint climb, you just
authenticate via OAuth and pass a single command,

12
00:00:41,382 --> 00:00:41,602
right?

13
00:00:42,062 --> 00:00:45,822
It's- it's just @DigitalOcean create a new
remote machine.

14
00:00:46,663 --> 00:00:47,252
Exactly.

15
00:00:47,983 --> 00:00:52,983
Once you run that, Codex talks to the
DigitalOcean API, provisions a Droplet

16
00:00:52,993 --> 00:00:56,593
pre-configured with what they're calling
the codex-universal stack,

17
00:00:57,303 --> 00:01:01,223
sets up the SSH keys, and then hands you
back a connection deep link.

18
00:01:01,923 --> 00:01:07,503
If you want to jump back in later, you
just run @DigitalOcean connect and pass the

19
00:01:07,583 --> 00:01:09,263
specific droplet ID.

20
00:01:10,130 --> 00:01:14,859
Okay, but what's actually inside this
codex-universal image?

21
00:01:15,339 --> 00:01:19,899
Because if I have to spend twenty minutes
installing system-level dependencies or

22
00:01:20,019 --> 00:01:23,919
native build tools every single time I
boot a remote machine,

23
00:01:23,959 --> 00:01:27,479
the developer experience completely falls
apart.

24
00:01:27,680 --> 00:01:29,480
Right, no, that's- that's a fair point.

25
00:01:29,860 --> 00:01:35,080
It's a standard Ubuntu base, but it comes
pre-loaded with common runtimes like Node,

26
00:01:35,580 --> 00:01:37,090
Python, and Docker.

27
00:01:37,680 --> 00:01:43,330
But if you need something highly
specialized, like, say, a specific CUDA toolkit or

28
00:01:43,360 --> 00:01:48,360
some obscure C++ library, you do have to
script that setup yourself.

29
00:01:49,000 --> 00:01:53,900
Codex doesn't magically sync your local
system packages to the cloud machine yet.

30
00:01:54,400 --> 00:01:56,809
Mm, so it's a clean slate.

31
00:01:56,909 --> 00:01:59,379
But the major upside is persistence.

32
00:01:59,869 --> 00:02:04,119
If my local machine hits a sleep timeout
or if I lose Wi-Fi for five minutes,

33
00:02:04,589 --> 00:02:08,519
the agent loop on the Droplet doesn't just
die mid-execution.

34
00:02:08,529 --> 00:02:11,119
It's completely isolated from my local
environment.

35
00:02:11,933 --> 00:02:12,913
Exactly.

36
00:02:12,953 --> 00:02:16,173
It completely avoids that local timeout
issue.

37
00:02:16,193 --> 00:02:18,993
But we have to talk about the billing side
of this.

38
00:02:19,093 --> 00:02:23,313
Since these Droplets are provisioned
directly inside your own DigitalOcean account,

39
00:02:23,943 --> 00:02:27,373
there's no automatic shutdown policy by
default.

40
00:02:27,433 --> 00:02:31,613
If you spin up a high-CPU instance and
forget about it over the weekend,

41
00:02:32,133 --> 00:02:33,893
you're footing that bill.

42
00:02:33,953 --> 00:02:38,833
You have to explicitly manage the
lifecycle and tear down the droplet when the task

43
00:02:38,873 --> 00:02:39,833
finishes.

44
00:02:40,181 --> 00:02:42,791
Which actually brings up an interesting
workflow detail.

45
00:02:43,391 --> 00:02:48,151
If the agent is running persistently on a
remote Droplet, how does that change how

46
00:02:48,171 --> 00:02:50,341
we monitor it when we're away from the
keyboard?

47
00:02:50,831 --> 00:02:53,031
Is there a handoff mechanism?

48
00:02:53,043 --> 00:02:53,552
There is.

49
00:02:54,083 --> 00:02:58,923
Because the state is preserved on the
cloud host, you can actually transition local

50
00:02:59,023 --> 00:03:01,843
agent sessions directly to your mobile
device.

51
00:03:01,883 --> 00:03:04,263
They've introduced a QR code pairing
system.

52
00:03:04,863 --> 00:03:09,063
You scan the code from your terminal, and
it securely syncs the active session

53
00:03:09,143 --> 00:03:11,823
thread straight to the ChatGPT mobile app.

54
00:03:12,483 --> 00:03:17,043
You can monitor the execution logs or even
give manual approvals while you're away

55
00:03:17,083 --> 00:03:17,643
from your desk.

56
00:03:19,008 --> 00:03:19,009
Huh.

57
00:03:19,078 --> 00:03:22,318
That's actually pretty slick for
long-running migrations.

58
00:03:23,078 --> 00:03:28,438
Now, speaking of automated tasks, I wanted
to ask about the new Record and Replay

59
00:03:28,478 --> 00:03:32,838
feature in macOS App version 26.616.

60
00:03:32,918 --> 00:03:38,158
Is this just a glorified macro recorder,
or is it actually generating structured

61
00:03:38,358 --> 00:03:39,438
skills for the agent?

62
00:03:40,200 --> 00:03:41,460
It's a bit of both, honestly.

63
00:03:42,040 --> 00:03:47,090
It captures your keyboard inputs, clicks,
and window context on macOS,

64
00:03:47,660 --> 00:03:52,860
but instead of outputting a rigid
screen-coordinate macro, it parses those actions

65
00:03:52,900 --> 00:03:54,830
into a declarative skill definition.

66
00:03:55,540 --> 00:04:01,529
So the agent can adapt the execution even
if, say, an application window is resized

67
00:04:01,940 --> 00:04:03,840
or a button moves slightly on the screen.

68
00:04:06,660 --> 00:04:08,150
Okay, that's a massive relief.

69
00:04:08,630 --> 00:04:13,320
There is nothing worse than a brittle UI
test or macro that breaks the second a

70
00:04:13,350 --> 00:04:14,830
pop-up appears.

71
00:04:14,930 --> 00:04:17,010
Let's touch on the CLI update before we
wrap.

72
00:04:17,489 --> 00:04:24,290
I saw Codex CLI 0.143.0-alpha dropped
yesterday to address a pretty

73
00:04:24,450 --> 00:04:25,250
nasty crash.

74
00:04:26,043 --> 00:04:32,883
Yeah, the 0.143.0-alpha release is
critical if you're using the Claude Code

75
00:04:32,963 --> 00:04:33,403
plugin.

76
00:04:34,043 --> 00:04:39,483
There was a strict schema validation bug
in the parser that caused a complete import

77
00:04:39,503 --> 00:04:44,883
validation crash whenever it encountered
certain nested configuration blocks.

78
00:04:44,892 --> 00:04:49,803
This alpha build resolves the parser
strictness so the import pipeline doesn't

79
00:04:49,853 --> 00:04:50,163
choke.

80
00:04:50,814 --> 00:04:51,823
Perfect.

81
00:04:51,833 --> 00:04:55,803
So if you're hitting that crash, run the
update to pull down the alpha patch.

82
00:04:56,383 --> 00:04:58,693
I think that covers our main updates for
today.

83
00:04:59,283 --> 00:05:03,003
I'm going to go play with this
DigitalOcean plugin and see if I can keep my laptop

84
00:05:03,043 --> 00:05:04,333
fans quiet for once.

85
00:05:05,231 --> 00:05:06,431
Sounds like a plan.

86
00:05:06,511 --> 00:05:07,591
Talk to you tomorrow, Maya.