1
00:00:00,080 --> 00:00:06,920
So, if you fired up Codex CLI version
0.157.0 today, you

2
00:00:07,000 --> 00:00:10,860
might not have even noticed, but the
terminal quieted down a lot.

3
00:00:11,580 --> 00:00:18,560
With pull request 47179, interactive
sessions now spin up a background server daemon

4
00:00:18,980 --> 00:00:19,660
automatically.

5
00:00:20,420 --> 00:00:24,480
You do not have to orchestrate background
processes manually anymore,

6
00:00:25,060 --> 00:00:26,180
it, it just happens.

7
00:00:26,900 --> 00:00:30,260
Quick thanks to Jellypod for supporting
our daily technical breakdown,

8
00:00:30,300 --> 00:00:30,740
by the way.

9
00:00:31,420 --> 00:00:35,420
But yeah, Maya, this changes the whole
developer experience for terminal sessions.

10
00:00:35,838 --> 00:00:41,958
Right, because previously, if you were
running complex subagent tasks or maintaining

11
00:00:42,078 --> 00:00:47,438
active git worktree checkouts, everything
lived and died right inside that single

12
00:00:47,498 --> 00:00:48,378
terminal process.

13
00:00:48,978 --> 00:00:52,518
If you accidentally closed your terminal
window or your shell crashed,

14
00:00:52,938 --> 00:00:56,298
boom, there goes your context, there go
your active logs.

15
00:00:57,158 --> 00:01:02,358
Now, when you open an interactive prompt,
it instantly attaches to or spins up a

16
00:01:02,458 --> 00:01:04,178
shared local background server.

17
00:01:04,778 --> 00:01:07,018
The server acts as a resilient anchor.

18
00:01:07,493 --> 00:01:08,033
Exactly.

19
00:01:08,653 --> 00:01:11,973
But, um, that creates a really interesting
operational problem.

20
00:01:12,613 --> 00:01:17,213
What happens when your current shell
environment changes, but that background daemon

21
00:01:17,253 --> 00:01:19,293
is still running on yesterday's
configuration?

22
00:01:19,753 --> 00:01:21,293
Ah, env drift!

23
00:01:21,853 --> 00:01:25,513
That used to be a nightmare with
persistent background services.

24
00:01:25,993 --> 00:01:30,933
Like, say you set new network proxy
settings, or you changed custom daemon socket

25
00:01:31,033 --> 00:01:35,833
paths, or maybe you exported a totally
different model override in your terminal.

26
00:01:36,493 --> 00:01:40,993
The daemon on the background server is
still using the old environment variables,

27
00:01:41,413 --> 00:01:46,093
so your new commands would either silently
fail or just hang indefinitely.

28
00:01:46,557 --> 00:01:50,357
Exactly where pull request 47318 comes in.

29
00:01:51,017 --> 00:01:57,917
Instead of failing silently, 0.157.0 pops
an interactive terminal recovery

30
00:01:58,037 --> 00:02:01,737
prompt the second it detects incompatible
server settings.

31
00:02:02,437 --> 00:02:06,417
You get three explicit choices right there
in the terminal user interface.

32
00:02:06,900 --> 00:02:09,320
Okay, walk me through those three choices.

33
00:02:09,880 --> 00:02:13,220
What can a developer actually do when that
prompt appears?

34
00:02:13,683 --> 00:02:18,643
Option one, you can choose to restart the
daemon using your fresh host environment

35
00:02:18,723 --> 00:02:19,183
variables.

36
00:02:20,043 --> 00:02:24,323
Option two, you can adopt the existing
server's settings for your new thread.

37
00:02:25,023 --> 00:02:28,963
Or option three, if you do not want to
disturb the running server at all,

38
00:02:29,483 --> 00:02:33,603
you can completely isolate your current
session into a standalone,

39
00:02:34,003 --> 00:02:35,123
independent process.

40
00:02:35,608 --> 00:02:37,668
That, that is so clean.

41
00:02:38,108 --> 00:02:42,788
It gives you full control without making
you guess why your proxy or model settings

42
00:02:42,828 --> 00:02:44,008
are not registering.

43
00:02:44,960 --> 00:02:50,700
Speaking of working across multiple
threads and sessions, pull request 47185 added

44
00:02:50,740 --> 00:02:53,840
something I have already used like ten
times today.

45
00:02:54,320 --> 00:02:59,740
It is a new keyboard shortcut in the
terminal interface, just press f to fork.

46
00:03:00,383 --> 00:03:03,543
Wait, how does that work if the thread is
currently being used by another

47
00:03:03,623 --> 00:03:04,063
application?

48
00:03:04,523 --> 00:03:05,803
That is the magic!

49
00:03:06,403 --> 00:03:11,503
Say you have a thread open and active
inside ChatGPT Desktop or an IDE plugin,

50
00:03:11,983 --> 00:03:14,603
and that thread is locked by that
application.

51
00:03:15,163 --> 00:03:17,803
Previously, you could not touch it from
your CLI.

52
00:03:18,463 --> 00:03:22,583
Now, hitting f creates a brand new thread
fork immediately.

53
00:03:23,183 --> 00:03:27,663
And get this, it preserves your
uncommitted drafts and any queued prompts you had

54
00:03:27,703 --> 00:03:30,143
waiting in the composer, so nothing gets
wiped.

55
00:03:31,282 --> 00:03:34,242
That solves a huge bottleneck for multi
app workflows.

56
00:03:34,842 --> 00:03:41,362
And to pair with that, pull request 47317
made the slash import command available

57
00:03:41,522 --> 00:03:41,942
everywhere.

58
00:03:42,662 --> 00:03:47,942
You can run slash import inside remote SSH
sessions, tmux setups,

59
00:03:48,442 --> 00:03:53,782
or local background server sessions to
pull external conversation logs straight into

60
00:03:53,802 --> 00:03:55,262
your active agent context.

61
00:03:55,795 --> 00:04:00,355
So you could take a chat history from a
completely different tool or remote machine

62
00:04:00,755 --> 00:04:05,495
and feed it directly to your running Codex
agent without copy pasting blocks of

63
00:04:05,555 --> 00:04:05,955
text.

64
00:04:06,453 --> 00:04:07,073
Exactly.

65
00:04:07,493 --> 00:04:14,053
And there are some really solid quality of
life updates in 0.157.0 that fix

66
00:04:14,213 --> 00:04:15,313
daily friction points.

67
00:04:15,993 --> 00:04:22,913
Pull request 47414 enables fullscreen
transcripts by default and lets you use Shift

68
00:04:23,033 --> 00:04:26,633
click to extend text selection across long
code blocks.

69
00:04:27,373 --> 00:04:34,353
Pull request 47417 fixes native
Terminal.app scrollback over SSH when

70
00:04:34,433 --> 00:04:38,673
automatic screen mode is active,
respecting your tmux mouse settings.

71
00:04:39,210 --> 00:04:42,510
Oh, SSH scrollback fixes are always a
blessing.

72
00:04:43,370 --> 00:04:44,890
Did they touch file uploads too?

73
00:04:45,555 --> 00:04:52,375
Yeah, pull request 47122 bumped the OpenAI
file blob upload timeout

74
00:04:52,435 --> 00:04:57,795
from sixty seconds to five minutes, plus
added automatic retries for transient

75
00:04:57,895 --> 00:04:58,635
network drops.

76
00:04:59,335 --> 00:05:04,635
So uploading large datasets or bundle
archives will not randomly time out anymore.

77
00:05:05,007 --> 00:05:10,447
Okay, but we have to talk about the
security change in pull request 47389.

78
00:05:10,947 --> 00:05:15,687
This one is super important if you run
agents in locked down corporate environments.

79
00:05:16,243 --> 00:05:17,883
What changed with network filtering?

80
00:05:18,378 --> 00:05:23,198
In earlier versions, network restrictions
were evaluated when a connection opened.

81
00:05:23,738 --> 00:05:30,198
But now, network access policy is
continuously enforced across all HTTP and

82
00:05:30,318 --> 00:05:33,678
WebSocket redirects, as well as ongoing
traffic.

83
00:05:34,498 --> 00:05:39,418
If an outbound request or a redirect
target tries to hop to an address that violates

84
00:05:39,458 --> 00:05:44,538
your workspace security rules, Codex
revokes access and severs the connection

85
00:05:44,758 --> 00:05:45,278
instantly.

86
00:05:45,805 --> 00:05:52,365
Wow, so an agent cannot be tricked by an
external HTTP redirect into bypassing local

87
00:05:52,485 --> 00:05:54,885
sandbox rules or network policies.

88
00:05:55,277 --> 00:05:56,117
Exactly.

89
00:05:56,717 --> 00:06:00,477
Between seamless daemon recovery, cross
app thread forking,

90
00:06:00,697 --> 00:06:07,417
and strict redirect security, 0.157.0 is a
massive step forward for

91
00:06:07,457 --> 00:06:08,897
reliability in the terminal.

92
00:06:09,533 --> 00:06:11,753
Yeah, definitely worth updating right
away.

93
00:06:12,453 --> 00:06:15,793
Alright, that is the breakdown for today,
talk to you next time.