1
00:00:00,099 --> 00:00:03,759
Your laptop fan starts screaming like a
jet engine, the, uh,

2
00:00:03,959 --> 00:00:09,119
local subshell binary hangs on a massive
compilation step, and suddenly your whole

3
00:00:09,179 --> 00:00:11,579
local environment is just locked up .

4
00:00:12,340 --> 00:00:13,519
We have all been there.

5
00:00:14,299 --> 00:00:18,040
Huge shoutout to Jellypod for helping us
bring you this show every day,

6
00:00:18,559 --> 00:00:23,879
because today we are talking about how
Codex zero point one hundred forty six point

7
00:00:24,059 --> 00:00:26,599
zero finally fixes that headache.

8
00:00:28,284 --> 00:00:32,025
Oh man, the dreaded local laptop meltdown.

9
00:00:32,644 --> 00:00:36,844
Wait, so what actually changed under the
hood in zero point fourteen six?

10
00:00:37,125 --> 00:00:41,525
So PR thirty five thousand seventy eight
and thirty five thousand ninety eight

11
00:00:41,605 --> 00:00:44,165
brought in native WebSocket support.

12
00:00:44,305 --> 00:00:49,525
You can now connect app server to remote
Code Mode hosts over WebSocket,

13
00:00:49,578 --> 00:00:52,725
using ws or wss protocol schemes.

14
00:00:53,194 --> 00:00:58,574
Wait, connect app server to remote Code
Mode hosts over WebSocket?

15
00:00:59,335 --> 00:01:04,835
So instead of spawning that local codex
code mode host wrapper or piping through

16
00:01:04,914 --> 00:01:10,274
fragile raw subshells on your own machine,
it just streams straight out to a remote

17
00:01:10,334 --> 00:01:10,734
server?

18
00:01:11,125 --> 00:01:12,205
Exactly.

19
00:01:12,298 --> 00:01:17,125
It completely decouples the tool execution
engine from your local machine.

20
00:01:17,205 --> 00:01:21,765
You can run a super lightweight IDE
extension or local terminal,

21
00:01:21,805 --> 00:01:27,205
and hand off all the heavy lifts, like
running test suites or containerized builds,

22
00:01:27,258 --> 00:01:31,125
to a beefy cloud devbox or a remote
Kubernetes pod.

23
00:01:31,484 --> 00:01:34,324
That is huge for thin client setups.

24
00:01:35,064 --> 00:01:37,764
How do you actually point Codex to a
remote box then?

25
00:01:38,045 --> 00:01:39,625
Is it just a single config setting?

26
00:01:39,958 --> 00:01:40,758
Pretty much, yeah.

27
00:01:40,898 --> 00:01:45,238
You set your remote Code Mode host URI in
your configuration,

28
00:01:45,278 --> 00:01:51,078
something like wss colon slash slash code
mode dot internal dot net,

29
00:01:51,222 --> 00:01:55,558
port eighty eighty, slash v1 slash ws.

30
00:01:55,702 --> 00:02:01,158
When app server boots, it initiates a
clean authenticated WebSocket handshake

31
00:02:01,247 --> 00:02:02,918
directly to that endpoint.

32
00:02:03,131 --> 00:02:05,718
No extra local host process required.

33
00:02:06,167 --> 00:02:11,827
So your laptop stays completely cool, and
all the actual execution happens somewhere

34
00:02:11,887 --> 00:02:15,987
else with low latency bidirectional
streaming back to your terminal.

35
00:02:16,532 --> 00:02:17,333
Right.

36
00:02:17,352 --> 00:02:21,753
But, uh, moving your execution across the
network brings its own set of weird

37
00:02:21,793 --> 00:02:25,213
quirks, especially once corporate networks
get involved .

38
00:02:26,152 --> 00:02:27,612
Ah, right!

39
00:02:27,952 --> 00:02:29,652
Enterprise firewalls!

40
00:02:30,713 --> 00:02:35,552
I bet those classic corporate middleboxes
love messing with WebSocket connections.

41
00:02:35,917 --> 00:02:37,277
Oh, absolutely.

42
00:02:37,437 --> 00:02:43,117
If an enterprise reverse proxy strips out
the HTTP Connection Upgrade header,

43
00:02:43,165 --> 00:02:46,077
that WebSocket handshake just drops dead
silently.

44
00:02:46,237 --> 00:02:51,517
And if a socket disconnects abruptly mid
execution, you risk leaving orphaned

45
00:02:51,573 --> 00:02:55,037
container processes churning away on your
remote server.

46
00:02:55,322 --> 00:02:58,421
That sounds like a nightmare for resource
leaks.

47
00:02:58,461 --> 00:03:01,901
Did they add anything in this release to
deal with unstable connections?

48
00:03:02,390 --> 00:03:02,909
They did.

49
00:03:03,490 --> 00:03:08,949
PR thirty four thousand seven hundred
sixty three introduced automated reconnection

50
00:03:09,190 --> 00:03:09,589
logic.

51
00:03:10,210 --> 00:03:14,229
If a network blip happens or response
frames drop mid turn,

52
00:03:14,829 --> 00:03:20,049
Codex automatically retries the WebSocket
connection and attempts to restore state

53
00:03:20,109 --> 00:03:21,729
without crashing your active session.

54
00:03:22,129 --> 00:03:23,729
That is such a relief.

55
00:03:24,389 --> 00:03:26,769
What about the actual terminal experience?

56
00:03:27,069 --> 00:03:30,329
Were there any other polish updates in
zero point fourteen six?

57
00:03:30,667 --> 00:03:34,027
A bunch of really nice quality of life
fixes, actually.

58
00:03:34,160 --> 00:03:39,627
PR thirty four thousand seven hundred
seventy five clamps session headers when you

59
00:03:39,647 --> 00:03:44,507
are working in super narrow terminal
layouts, so text stopped getting garbled.

60
00:03:44,635 --> 00:03:51,067
Then PR thirty four thousand seven hundred
seventy eight coalesces wrapped OSC eight

61
00:03:51,147 --> 00:03:51,947
hyperlinks.

62
00:03:52,377 --> 00:03:54,658
Wait, OSC eight links?

63
00:03:55,178 --> 00:03:59,958
You mean when a long URL wraps across two
lines in your terminal and breaks the

64
00:04:00,037 --> 00:04:00,718
clickable link?

65
00:04:01,083 --> 00:04:02,243
Precisely!

66
00:04:02,333 --> 00:04:07,483
Now those wrapped links stay fully
clickable as a single unified URL.

67
00:04:07,623 --> 00:04:12,923
And PR thirty five thousand added non
blocking Control C interrupts,

68
00:04:12,976 --> 00:04:18,203
so pressing Control C actually cancels
host commands immediately without freezing up

69
00:04:18,235 --> 00:04:19,323
your terminal UI.

70
00:04:19,712 --> 00:04:24,372
Honestly, before any team deploys remote
Code Mode hosts at scale,

71
00:04:24,852 --> 00:04:29,452
they should really audit their internal
proxy rules and container lifecycle cleanup

72
00:04:29,512 --> 00:04:29,992
routines.

73
00:04:30,592 --> 00:04:36,833
But man, being able to offload execution
cleanly over WebSockets changes everything

74
00:04:36,933 --> 00:04:38,152
for lightweight dev rigs.

75
00:04:38,417 --> 00:04:39,777
It really does.

76
00:04:39,827 --> 00:04:43,697
Alright, that is the latest in Codex zero
point fourteen six.

77
00:04:43,830 --> 00:04:45,297
Catch you next time!