1
00:00:00,000 --> 00:00:04,159
Hey Maya, I spent the morning digging into
the release notes for Codex version

2
00:00:04,399 --> 00:00:10,557
0.136.0, and they've finally addressed a
massive headache for anyone running

3
00:00:10,621 --> 00:00:15,043
automated agent workflows: session
mutation.

4
00:00:15,100 --> 00:00:18,240
Thanks to Jellypod to help make this daily
show a reality.

5
00:00:19,050 --> 00:00:22,559
Powered by Jellypod AI, we're unpacking
how they did it.

6
00:00:23,000 --> 00:00:29,040
Ugh the classic accidentally resumed an
old run and corrupted my entire state

7
00:00:29,040 --> 00:00:34,240
disaster I can't tell you how many times
we had testers run into state corruption

8
00:00:34,240 --> 00:00:39,020
because an old session was forked or
resumed by mistake during collaborative

9
00:00:39,020 --> 00:00:41,118
debugging Exactly.

10
00:00:41,225 --> 00:00:46,562
In 0.136.0, they've introduced explicit
session archiving.

11
00:00:46,829 --> 00:00:53,203
If you're on the CLI, you run `codex
archive`, or if you prefer the TUI,

12
00:00:53,243 --> 00:00:55,604
you just type `/archive`.

13
00:00:55,791 --> 00:00:58,480
It completely freezes the session history.

14
00:00:59,000 --> 00:01:05,980
So once it's frozen it's read only No
accidental restarts No appending new

15
00:01:05,980 --> 00:01:07,878
agent steps Exactly.

16
00:01:08,011 --> 00:01:10,830
It blocks resumption and forking
completely.

17
00:01:11,043 --> 00:01:16,106
If you actually want to modify it later,
you have to run an explicit `codex

18
00:01:16,213 --> 00:01:17,630
unarchive` first.

19
00:01:17,817 --> 00:01:20,986
It forces a deliberate, manual speed bump.

20
00:01:22,000 --> 00:01:28,380
Which is perfect honestly From a QA
perspective safety shouldn't rely on developers

21
00:01:28,380 --> 00:01:33,720
remembering not to press a button But how
does this affect state storage Is it

22
00:01:33,720 --> 00:01:38,880
actually compressing the history or just
setting a metadata flag It's primarily a

23
00:01:38,947 --> 00:01:43,986
state-locking metadata layer, but it
prevents any write operations to that specific

24
00:01:44,036 --> 00:01:44,786
session path.

25
00:01:44,986 --> 00:01:49,344
Let's say you're working in a shared team
environment where multiple devs are

26
00:01:49,397 --> 00:01:54,939
querying agent run history-this guarantees
the integrity of those past runs without

27
00:01:54,983 --> 00:01:58,539
worrying about someone polluting the token
history or memory buffers.

28
00:01:59,000 --> 00:02:04,300
Right because if another team member pulls
down your session to analyze how the

29
00:02:04,300 --> 00:02:08,840
agent solved a complex problem they might
run a command that triggers a fresh

30
00:02:08,840 --> 00:02:14,700
execution loop by mistake That slash
archive command ensures that history remains a

31
00:02:14,700 --> 00:02:18,078
pure untouched record Exactly.

32
00:02:18,148 --> 00:02:25,075
Now, speaking of security and integrity,
version 0.136.0 also does some

33
00:02:25,145 --> 00:02:30,518
serious hardening on the security side,
specifically around the `/diff` command.

34
00:02:31,000 --> 00:02:37,180
Wait diff Isn't that just showing file
differences How do you get an execution

35
00:02:37,180 --> 00:02:42,120
vector out of a diff command Well,
malicious repositories can craft custom git

36
00:02:42,179 --> 00:02:47,647
configurations or file headers that trick
diff parsers into executing arbitrary

37
00:02:47,709 --> 00:02:48,285
commands.

38
00:02:48,415 --> 00:02:55,163
Version 0.136.0 completely blocks those
repository-provided

39
00:02:55,243 --> 00:02:56,523
execution vectors.

40
00:02:57,000 --> 00:03:03,820
Ah git exploit vectors Hmm that makes
sense If you're pulling down an

41
00:03:03,820 --> 00:03:08,900
untrusted open source repo to review it
the last thing you want is the agent's code

42
00:03:08,900 --> 00:03:12,840
review command executing arbitrary shell
scripts hidden in the diff metadata

43
00:03:13,000 --> 00:03:13,799
Precisely.

44
00:03:13,979 --> 00:03:18,990
Codex is limiting what can be parsed and
executed when inspecting external

45
00:03:19,058 --> 00:03:20,434
repositories.

46
00:03:20,474 --> 00:03:24,268
And speaking of execution environments, if
you're on Windows,

47
00:03:24,284 --> 00:03:27,631
they've introduced an alpha path for
sandbox provisioning.

48
00:03:27,751 --> 00:03:32,828
You run `codex sandbox setup --elevated`.

49
00:03:33,000 --> 00:03:38,760
Wait elevated Does that mean it needs full
administrator privileges to spin up the

50
00:03:38,760 --> 00:03:40,960
container sandbox It does.

51
00:03:41,000 --> 00:03:46,316
Because Windows sandbox APIs and Hyper-V
features require admin privileges to

52
00:03:46,372 --> 00:03:50,231
configure network bridges and virtual
machines properly.

53
00:03:50,258 --> 00:03:54,873
It's a bit of a hurdle, but it's a huge
step toward parity with Linux container

54
00:03:54,937 --> 00:03:55,753
sandboxes.

55
00:03:56,000 --> 00:04:01,780
Right but running commands with admin
privileges always makes security teams sweat

56
00:04:02,280 --> 00:04:07,340
Is there any plan to allow non elevated
setups later or is this just the price of

57
00:04:07,340 --> 00:04:11,442
admission for native Windows sandboxing
They're calling this an alpha path

58
00:04:11,504 --> 00:04:13,682
specifically because of that complexity.

59
00:04:13,842 --> 00:04:18,559
For now, it's about getting the Hyper-V
containers provisioned securely,

60
00:04:18,579 --> 00:04:21,931
and they'll likely refine the permission
model in later releases.

61
00:04:22,000 --> 00:04:27,940
Fair enough But hey let's talk about
something a bit more satisfying for the

62
00:04:27,940 --> 00:04:32,599
terminal daily drivers - OSC8 links Yes!

63
00:04:32,649 --> 00:04:35,753
The terminal experience is getting a
massive upgrade.

64
00:04:35,849 --> 00:04:41,507
They've integrated OSC 8 metadata, which
means when Codex outputs markdown with

65
00:04:41,574 --> 00:04:46,948
links, your terminal actually renders them
as native, clickable hyperlinks.

66
00:04:47,000 --> 00:04:53,840
Finally no more dragging my mouse to copy
paste an entire long URL from a

67
00:04:53,840 --> 00:04:59,520
terminal pane into a browser window If my
terminal emulator supports OSC 8 I can

68
00:04:59,520 --> 00:05:04,841
just control click it It's a tiny detail,
but for a tool you live in all day,

69
00:05:04,894 --> 00:05:07,081
it's a huge quality-of-life win.

70
00:05:07,241 --> 00:05:13,801
That's version 0.136.0 for you: locking
down past runs,

71
00:05:13,872 --> 00:05:18,037
securing your diffs, and making the
terminal just a little less painful.

72
00:05:19,000 --> 00:05:24,900
I'll take clickable links and locked
histories any day Let's see how that sandbox

73
00:05:24,900 --> 00:05:27,100
setup behaves on our Windows test suite
next