1
00:00:00,280 --> 00:00:05,120
So Codex 0.163.0 is out of prerelease.

2
00:00:05,880 --> 00:00:09,400
Thanks to Jellypod for helping make this
daily show a reality.

3
00:00:10,460 --> 00:00:15,560
Last time we were poking at the Program
Status Protocol signals in alpha 11,

4
00:00:16,160 --> 00:00:19,400
while stable was still sitting on 0.162.1.

5
00:00:20,540 --> 00:00:26,560
As of October 15th, 0.163.0 is the stable
release, and the

6
00:00:26,680 --> 00:00:31,000
0.164.0 alpha 1 tag already showed up this
morning.

7
00:00:32,000 --> 00:00:36,440
The headline feature in this one is the
new interactive /config command.

8
00:00:37,143 --> 00:00:38,483
The way I'd frame it is this.

9
00:00:39,083 --> 00:00:44,123
Until now, changing a setting meant
opening config.toml, remembering the exact key

10
00:00:44,203 --> 00:00:48,163
name, saving, and then wondering whether
the running session ever noticed.

11
00:00:48,843 --> 00:00:53,223
Now you type /config inside a session and
it opens a preferences manager.

12
00:00:53,963 --> 00:00:57,803
According to the release notes, you can
search preferences across categories,

13
00:00:58,003 --> 00:01:02,343
change supported settings immediately, and
see which changes require a restart.

14
00:01:02,983 --> 00:01:04,763
Those are the three things that used to be
guesswork.

15
00:01:05,303 --> 00:01:10,303
Pull requests 52990 and 53429 are the ones
to look at.

16
00:01:10,913 --> 00:01:13,873
The phrase to hold onto is "supported
settings."

17
00:01:14,593 --> 00:01:15,933
Not everything applies live.

18
00:01:16,873 --> 00:01:20,673
The release notes say the interface tells
you which changes need a restart,

19
00:01:21,253 --> 00:01:25,193
so the first habit to build is reading
that indicator instead of assuming.

20
00:01:26,393 --> 00:01:30,713
If a setting applies immediately, you flip
it and keep working in the same thread.

21
00:01:31,313 --> 00:01:35,513
If it doesn't, you know before you waste
ten minutes wondering why nothing changed.

22
00:01:35,990 --> 00:01:38,110
And that's where the companion piece
matters.

23
00:01:38,330 --> 00:01:43,470
0.163.0 also adds a restart action under
/daemon.

24
00:01:44,110 --> 00:01:46,070
It restarts a managed background server.

25
00:01:46,550 --> 00:01:50,710
The changelog says Codex warns you about
work the restart could interrupt,

26
00:01:51,270 --> 00:01:52,810
and then reconnects automatically.

27
00:01:53,510 --> 00:01:57,810
So the workflow looks like this: open
/config, search for the setting,

28
00:01:58,190 --> 00:01:58,610
change it.

29
00:01:59,190 --> 00:02:03,490
If it's flagged as needing a restart, run
/daemon, read the warning,

30
00:02:03,810 --> 00:02:04,350
and confirm.

31
00:02:04,870 --> 00:02:08,650
You come back to the same session without
relaunching the terminal UI.

32
00:02:09,432 --> 00:02:12,612
Let me make that concrete, because the
warning is the important part.

33
00:02:13,372 --> 00:02:17,352
Say you've kicked off a long task and you
decide you want a different configuration.

34
00:02:18,152 --> 00:02:22,292
Before this release, you might have killed
a process from another shell and lost the

35
00:02:22,352 --> 00:02:23,312
thread of what was running.

36
00:02:24,112 --> 00:02:28,312
Now the restart flow tells you up front
that in flight work could be interrupted.

37
00:02:29,252 --> 00:02:34,792
Our research notes also suggest that
subagents or child processes spawned by tools

38
00:02:35,292 --> 00:02:36,652
would be aborted on restart.

39
00:02:37,412 --> 00:02:41,392
That detail isn't spelled out in the
release notes, so test it before you rely on

40
00:02:41,432 --> 00:02:41,592
it.

41
00:02:42,192 --> 00:02:45,612
The safe move is to let active turns
finish first, then restart.

42
00:02:46,215 --> 00:02:51,255
Which brings us to caveats, and I want to
separate what's confirmed from what's

43
00:02:51,275 --> 00:02:52,075
worth verifying.

44
00:02:52,655 --> 00:02:56,735
Confirmed: the release notes describe
search, immediate changes,

45
00:02:57,015 --> 00:03:00,275
and restart indicators, plus the daemon
restart warning.

46
00:03:00,835 --> 00:03:05,375
Our notes also say that enterprise managed
configuration stays authoritative,

47
00:03:05,795 --> 00:03:09,175
so settings set by an administrator policy
would show as locked,

48
00:03:09,695 --> 00:03:13,495
and that flags you pass at startup, like a
model or a search flag,

49
00:03:14,035 --> 00:03:16,395
override file values for that session.

50
00:03:16,935 --> 00:03:20,115
Those make sense given how Codex has
treated precedence before,

51
00:03:20,515 --> 00:03:21,935
but check them in your own setup.

52
00:03:22,655 --> 00:03:23,135
One more thing.

53
00:03:23,615 --> 00:03:27,815
The notes say changes get written to the
active profile's config file.

54
00:03:28,315 --> 00:03:32,515
If you use named profiles, look at which
file changed after your first edit.

55
00:03:33,245 --> 00:03:34,465
A practical test is cheap.

56
00:03:35,185 --> 00:03:40,485
Run /config, change one setting, then open
your config file in another pane and see

57
00:03:40,545 --> 00:03:41,405
what landed where.

58
00:03:42,165 --> 00:03:45,925
If you keep your config in version
control, that diff also tells you whether the

59
00:03:45,985 --> 00:03:47,465
tool wrote what you thought you set.

60
00:03:48,385 --> 00:03:52,665
And if you've been maintaining a pile of
notes about which keys hot reload and which

61
00:03:52,725 --> 00:03:56,785
don't, this is the release where you can
start deleting those notes and trusting the

62
00:03:56,805 --> 00:03:57,545
interface instead.

63
00:03:58,205 --> 00:04:02,205
Now the smaller items, and a few of these
will change your day more than you'd

64
00:04:02,245 --> 00:04:02,685
expect.

65
00:04:03,225 --> 00:04:04,485
First, steering.

66
00:04:04,965 --> 00:04:09,545
You can send a follow up while Codex is
still responding, and it steers the turn

67
00:04:09,665 --> 00:04:10,225
immediately.

68
00:04:10,885 --> 00:04:15,365
Interrupting a turn now also stops active
Code Mode cells and their nested tool

69
00:04:15,445 --> 00:04:15,705
calls.

70
00:04:16,345 --> 00:04:20,805
The changelog lists instant interrupts and
Code Mode interruption as enabled by

71
00:04:20,825 --> 00:04:22,565
default, so you don't opt in.

72
00:04:23,265 --> 00:04:24,505
Second, the keymap.

73
00:04:24,725 --> 00:04:27,625
/keymap now lets you configure a leader
key.

74
00:04:28,445 --> 00:04:32,985
The default is Ctrl+X, shortcut hints stay
open until you choose or cancel,

75
00:04:33,665 --> 00:04:35,625
and voice mute moves to F9.

76
00:04:36,325 --> 00:04:40,845
If you had muscle memory or a terminal
binding on Ctrl+X, check for a collision.

77
00:04:41,625 --> 00:04:47,085
Our notes say the F9 move was meant to
avoid clashes with multiplexers like tmux,

78
00:04:47,585 --> 00:04:50,305
but that's an inference, not something the
release notes state.

79
00:04:51,098 --> 00:04:52,258
Third, performance.

80
00:04:52,678 --> 00:04:57,358
Codex can now run independent read only
tools in parallel, including skill,

81
00:04:57,838 --> 00:05:00,098
memory, and conversation history lookups.

82
00:05:00,758 --> 00:05:04,498
That's the context gathering phase, so
you'd mostly notice it at the start of a

83
00:05:04,538 --> 00:05:04,718
turn.

84
00:05:05,618 --> 00:05:09,978
Fourth, resuming a saved thread restores
its permissions and network approvals,

85
00:05:10,378 --> 00:05:13,998
while still respecting explicit overrides
and current managed policy.

86
00:05:14,638 --> 00:05:18,178
That means fewer repeated approval prompts
when you pick up yesterday's work.

87
00:05:18,790 --> 00:05:22,950
On security, the network proxy got three
fixes.

88
00:05:23,750 --> 00:05:29,730
It now checks hostname permission before a
DNS lookup, it rejects duplicate Host

89
00:05:29,810 --> 00:05:35,550
headers, and it stops credential aliases
from bypassing inspection hooks.

90
00:05:36,650 --> 00:05:42,090
If you run sandboxed sessions with a
network allowlist, that's worth knowing is in

91
00:05:42,130 --> 00:05:43,090
the stable channel now.

92
00:05:43,940 --> 00:05:45,020
Two housekeeping items.

93
00:05:45,680 --> 00:05:50,780
Codex no longer bundles a patched zsh and
uses its standard shell executor instead.

94
00:05:51,420 --> 00:05:55,220
If your config still uses the retired
shell flags, you'll get a migration notice,

95
00:05:55,500 --> 00:05:57,620
so read it rather than dismissing it.

96
00:05:58,320 --> 00:06:03,120
And on Windows, Ctrl+V and Shift+Insert
now paste text as well as images,

97
00:06:03,600 --> 00:06:08,680
while WSL reuses the clipboard reader and
copy attempts time out instead of hanging.

98
00:06:09,513 --> 00:06:10,753
So here's what to do today.

99
00:06:11,533 --> 00:06:18,253
Update to 0.163.0, open /config, search
for one setting you normally

100
00:06:18,373 --> 00:06:22,133
edit by hand, and watch whether it says it
needs a restart.

101
00:06:22,793 --> 00:06:26,653
If it does, use /daemon only when nothing
important is running.

102
00:06:27,193 --> 00:06:30,133
Then check your config file to see which
profile took the change.

103
00:06:30,993 --> 00:06:34,973
That's ten minutes, and you'll know
exactly how this behaves on your machine.