1
00:00:00,100 --> 00:00:00,760
Picture this.

2
00:00:01,300 --> 00:00:06,340
You ask a coding agent for a small change,
and it starts streaming dozens of lines

3
00:00:06,380 --> 00:00:08,100
down the wrong architectural path.

4
00:00:08,640 --> 00:00:09,280
And you just...

5
00:00:10,840 --> 00:00:11,500
watch it go.

6
00:00:11,865 --> 00:00:12,965
Oh, I've been there.

7
00:00:13,485 --> 00:00:14,445
You get two choices.

8
00:00:15,005 --> 00:00:18,605
Let the tokens burn, or hit Control C and
kill the whole turn.

9
00:00:18,875 --> 00:00:19,275
Right.

10
00:00:19,355 --> 00:00:24,635
So, um, Codex 0.159.0 has an answer.

11
00:00:24,782 --> 00:00:29,035
Quick thanks to Jellypod for helping make
this daily briefing happen,

12
00:00:29,075 --> 00:00:33,755
and everything I'm quoting comes from the
release notes on the Codex GitHub page.

13
00:00:34,212 --> 00:00:35,472
Okay, so what's the answer?

14
00:00:35,875 --> 00:00:38,675
An opt in setting called
instant_interrupt.

15
00:00:38,755 --> 00:00:44,995
You set it to true in config.toml, and
then new input can steer Codex during model

16
00:00:45,067 --> 00:00:48,595
responses, or during long running Code
Mode calls.

17
00:00:48,755 --> 00:00:54,835
The notes credit pakrym-oai, pull requests
48135 and

18
00:00:54,995 --> 00:00:56,875
48141.

19
00:00:56,985 --> 00:01:01,795
One lets Code Mode yield on new input, the
other preempts the model response.

20
00:01:02,093 --> 00:01:02,773
Preempts.

21
00:01:02,993 --> 00:01:05,413
So it stops the stream mid sentence?

22
00:01:05,708 --> 00:01:07,428
That's my reading of it, yeah.

23
00:01:07,518 --> 00:01:12,188
The model's turn gets cut in on, rather
than you waiting for it to finish.

24
00:01:12,448 --> 00:01:14,388
Hmm, but here's my worry.

25
00:01:14,928 --> 00:01:17,448
If I interrupt, don't I lose everything?

26
00:01:17,988 --> 00:01:20,808
Fresh session, the agent forgets what we
were doing.

27
00:01:21,203 --> 00:01:23,263
That's the part I, I, I wanted to check.

28
00:01:24,043 --> 00:01:25,583
Two other entries matter here.

29
00:01:26,203 --> 00:01:32,603
Pull request 48508 says it preserves
WebSocket continuations when steering a turn.

30
00:01:33,243 --> 00:01:35,963
So the live connection carries on instead
of resetting.

31
00:01:36,488 --> 00:01:38,868
So it's a nudge, not a restart.

32
00:01:39,250 --> 00:01:40,490
Exactly that.

33
00:01:40,537 --> 00:01:43,970
Think of a batch job versus a
conversation.

34
00:01:44,050 --> 00:01:46,370
Before, a turn was a batch job.

35
00:01:46,490 --> 00:01:48,370
You submit, you wait.

36
00:01:48,550 --> 00:01:52,130
Now it's more like tapping a colleague on
the shoulder while they're typing.

37
00:01:52,567 --> 00:01:53,687
And the security side?

38
00:01:54,227 --> 00:01:56,547
Codex has that Guardian review thing.

39
00:01:56,875 --> 00:01:59,435
Pull request 48725.

40
00:01:59,622 --> 00:02:04,075
It retains confirmed Code Mode messages
for Guardian reviews.

41
00:02:04,182 --> 00:02:08,155
So the reviewer doesn't get amnesia when
you redirect mid turn.

42
00:02:08,687 --> 00:02:10,127
Okay, good.

43
00:02:10,287 --> 00:02:14,067
Now my tester brain kicks in, because
there's a caveat.

44
00:02:14,667 --> 00:02:17,007
When you interrupt, what shows up on
screen?

45
00:02:17,375 --> 00:02:19,055
A short, neutral notice.

46
00:02:19,199 --> 00:02:22,495
Pull request 48830.

47
00:02:22,595 --> 00:02:23,855
Not an error state.

48
00:02:24,135 --> 00:02:27,995
Which I like, because an interruption you
caused on purpose shouldn't look like a

49
00:02:28,055 --> 00:02:28,475
crash.

50
00:02:29,135 --> 00:02:32,215
But, uh, and this is me reasoning, not
something the notes say,

51
00:02:32,675 --> 00:02:35,235
a clean banner doesn't undo anything.

52
00:02:35,595 --> 00:02:39,195
If a bash command already wrote files to
disk before your interrupt landed,

53
00:02:39,695 --> 00:02:41,215
those files are still there.

54
00:02:41,667 --> 00:02:42,947
Yeah, that's fair.

55
00:02:43,054 --> 00:02:45,587
Steering changes what happens next.

56
00:02:45,747 --> 00:02:48,307
It doesn't rewind what already happened.

57
00:02:48,673 --> 00:02:48,853
Right.

58
00:02:48,953 --> 00:02:51,153
So check your working tree after you
steer.

59
00:02:51,433 --> 00:02:52,953
Don't assume the slate is clean.

60
00:02:53,333 --> 00:02:55,493
Okay, so that's the headline feature.

61
00:02:55,653 --> 00:03:01,813
But 0.159.0 has a security piece I think
people will skip past.

62
00:03:02,113 --> 00:03:03,273
The AWS thing?

63
00:03:03,583 --> 00:03:03,903
Yep.

64
00:03:03,999 --> 00:03:10,383
Pull request 48176 protects .aws
directories by default under

65
00:03:10,463 --> 00:03:12,343
sandbox writable roots.

66
00:03:12,463 --> 00:03:17,343
So if you've given Codex a writable folder
that happens to contain your AWS

67
00:03:17,396 --> 00:03:19,823
credentials, those stay protected.

68
00:03:20,213 --> 00:03:23,173
Which is the kind of mistake that happens
at five p.m.

69
00:03:23,493 --> 00:03:24,233
on a Friday.

70
00:03:25,103 --> 00:03:25,543
Totally.

71
00:03:25,963 --> 00:03:31,943
And pull request 48155 says approved
commands keep explicit filesystem denials.

72
00:03:32,603 --> 00:03:35,923
So approving a command doesn't quietly
wipe out a rule you set.

73
00:03:36,298 --> 00:03:38,258
Wait, that could happen before?

74
00:03:38,625 --> 00:03:41,585
The fix exists, so I'd assume it was a
gap.

75
00:03:41,865 --> 00:03:44,225
I can't say how often it bit anyone.

76
00:03:44,510 --> 00:03:44,750
Fair.

77
00:03:45,230 --> 00:03:46,450
What about the patch releases?

78
00:03:46,550 --> 00:03:48,050
There were a couple right behind it.

79
00:03:48,333 --> 00:03:49,093
Two.

80
00:03:49,453 --> 00:03:56,013
0.159.1 added GPT 6.1 Sol as the

81
00:03:56,073 --> 00:04:02,413
default model in the bundled catalog and
Amazon Bedrock Mantle and Runtime catalogs.

82
00:04:02,541 --> 00:04:08,093
Pull requests 49323 and 49342.

83
00:04:08,189 --> 00:04:14,733
Then 0.159.2, pull request 49385,

84
00:04:14,820 --> 00:04:19,853
suppressed console windows flashing on
Windows when Codex launches background

85
00:04:19,933 --> 00:04:22,493
processes and sandboxed commands.

86
00:04:23,180 --> 00:04:24,100
I love that one.

87
00:04:24,560 --> 00:04:27,220
Little black boxes popping up and
vanishing.

88
00:04:27,560 --> 00:04:31,360
Nobody writes a blog post about it, but
everyone on Windows notices.

89
00:04:31,667 --> 00:04:33,827
Yeah, the boring fixes are the ones you
feel.

90
00:04:34,193 --> 00:04:36,933
Speaking of feel, there are some nice
small ones.

91
00:04:37,493 --> 00:04:41,853
You can scroll the transcript with the
mouse wheel while a plan approval modal is

92
00:04:41,952 --> 00:04:42,233
open.

93
00:04:42,713 --> 00:04:45,073
Pull request 48805.

94
00:04:45,753 --> 00:04:49,953
Before, you'd have to decide whether to
implement a plan without rereading it.

95
00:04:50,250 --> 00:04:52,410
That's a, a, a real annoyance fixed.

96
00:04:52,737 --> 00:04:56,337
And in the warnings viewer, closing it
dismisses the warnings you've looked at,

97
00:04:56,677 --> 00:04:58,457
and pressing k keeps one for later.

98
00:04:58,837 --> 00:05:00,837
Pull request 48205.

99
00:05:01,125 --> 00:05:02,565
And something got removed, right?

100
00:05:02,843 --> 00:05:08,023
The automatic follow up prompt
suggestions, and the tui.prompt_suggestions setting

101
00:05:08,063 --> 00:05:08,343
with them.

102
00:05:08,843 --> 00:05:10,883
Pull request 48621.

103
00:05:11,363 --> 00:05:11,923
Less clutter.

104
00:05:12,208 --> 00:05:14,288
Okay, so here's what I keep wondering.

105
00:05:14,528 --> 00:05:18,208
If steering is cheap, does it change how
people work?

106
00:05:18,352 --> 00:05:21,968
Like, do you start typing half a thought
and fix it as you go?

107
00:05:22,340 --> 00:05:27,000
Or do you burn more context with a dozen
tiny corrections?

108
00:05:27,620 --> 00:05:30,300
Every nudge is more text in the session.

109
00:05:30,583 --> 00:05:30,903
Hmm.

110
00:05:30,967 --> 00:05:32,023
That's the tradeoff.

111
00:05:32,163 --> 00:05:34,663
The notes don't measure it, so I'm
guessing.

112
00:05:34,783 --> 00:05:39,463
But I'd say exploratory wins when the
early direction is cheap to fix.

113
00:05:39,983 --> 00:05:40,903
I'd put it differently.

114
00:05:41,303 --> 00:05:44,603
Steer early, when the wrong path is ten
lines long.

115
00:05:44,803 --> 00:05:47,783
Not when it's two hundred, and already
touched your files.

116
00:05:48,083 --> 00:05:49,043
Ha, okay.

117
00:05:49,203 --> 00:05:50,563
Steer early.

118
00:05:50,611 --> 00:05:51,843
That's the takeaway.

119
00:05:52,215 --> 00:05:52,715
Good chat.

120
00:05:52,995 --> 00:05:53,935
Go check your config.