1
00:00:00,179 --> 00:00:04,500
So, I was looking through the zero point
one four six point zero release of Codex,

2
00:00:05,099 --> 00:00:09,599
and, uh, the thing that immediately jumped
out at me is how they are handling agent

3
00:00:09,679 --> 00:00:11,000
plugins now.

4
00:00:11,039 --> 00:00:14,839
It is, it is basically trying to kill off
toolchain fragmentation.

5
00:00:15,134 --> 00:00:19,315
Wait, zero point one four six point zero?

6
00:00:20,114 --> 00:00:23,314
What did they, what did they actually
change with plugins?

7
00:00:23,704 --> 00:00:27,224
They introduced support for standardized
Agent Plugins manifests.

8
00:00:27,744 --> 00:00:33,385
It is a file called dot codex slash plugin
point manifest point json,

9
00:00:33,925 --> 00:00:36,264
and it works with workspace plugin
publishing.

10
00:00:36,924 --> 00:00:38,505
But here is the big part, Maya.

11
00:00:39,085 --> 00:00:43,904
This same manifest format works across
Amazon Bedrock, Claude Code,

12
00:00:44,324 --> 00:00:45,064
and Codex.

13
00:00:46,144 --> 00:00:52,144
Wait, so Amazon Bedrock and Claude Code
are using the exact same plugin manifest?

14
00:00:52,944 --> 00:00:57,804
That, that actually means you do not have
to write custom wrappers for every single

15
00:00:57,965 --> 00:00:59,125
AI toolchain anymore.

16
00:00:59,776 --> 00:01:00,676
Exactly!

17
00:01:00,736 --> 00:01:05,716
You package your AI skills once with
defined permissions, resource paths,

18
00:01:06,056 --> 00:01:10,536
and tool schemas, and it just runs across
those different agent environments.

19
00:01:11,257 --> 00:01:13,776
No more vendor locked command line
extensions.

20
00:01:14,113 --> 00:01:19,552
Okay, so walk me through how this actually
works in a real project.

21
00:01:19,632 --> 00:01:20,932
Where do these files live?

22
00:01:21,512 --> 00:01:26,932
Right, so in your local workspace, you
structure your plugins under dot codex slash

23
00:01:27,092 --> 00:01:27,612
plugins.

24
00:01:28,313 --> 00:01:31,032
And let us say you update a manifest while
you are working.

25
00:01:31,692 --> 00:01:35,572
You do not have to kill your active TUI
session to pick up the changes.

26
00:01:36,192 --> 00:01:40,532
You just run codex plugin list space,
force refetch...

27
00:01:40,912 --> 00:01:46,652
wait, no, scratch the dashes, you run
codex plugin list with the force refetch flag.

28
00:01:47,808 --> 00:01:50,807
The force refetch flag, got it.

29
00:01:50,847 --> 00:01:56,108
So it reloads updated manifests on the fly
while your terminal session stays

30
00:01:56,147 --> 00:01:57,287
completely alive?

31
00:01:57,583 --> 00:01:58,943
Yep, on the fly.

32
00:01:59,103 --> 00:02:02,463
And when you want to share these custom
tools with your team,

33
00:02:02,483 --> 00:02:05,983
you just check that manifest directly into
your project repository.

34
00:02:06,090 --> 00:02:11,103
Everyone on the repo gets the exact same
custom tools instantly,

35
00:02:11,153 --> 00:02:14,143
without needing any external public plugin
registry.

36
00:02:14,319 --> 00:02:16,559
Oh, that is huge for team setup.

37
00:02:17,059 --> 00:02:21,659
I remember at my old job, getting everyone
on the exact same local script version

38
00:02:21,799 --> 00:02:23,659
was an absolute nightmare.

39
00:02:24,219 --> 00:02:28,460
Having it checked into git under dot codex
means zero setup friction.

40
00:02:28,951 --> 00:02:30,032
It really is.

41
00:02:30,071 --> 00:02:34,551
But, um, you know, when you start pulling
in remote plugin dependencies across

42
00:02:34,651 --> 00:02:38,592
workspaces, security becomes the immediate
elephant in the room.

43
00:02:39,064 --> 00:02:45,204
Right, because if an agent can execute
remote plugin code, a malicious or tampered

44
00:02:45,244 --> 00:02:49,564
manifest could just execute arbitrary
stuff on your machine during an update.

45
00:02:49,996 --> 00:02:50,657
Precisely.

46
00:02:51,196 --> 00:02:56,896
So in pull request thirty four six four
four, they enforced mandatory Git commit SHA

47
00:02:56,956 --> 00:03:00,396
verification when you pin remote plugin
dependencies.

48
00:03:01,116 --> 00:03:06,156
Combined with PR thirty four five nine
seven for exact managed configuration

49
00:03:06,276 --> 00:03:12,257
policies, Codex basically blocks
unauthorized code execution when plugins pull down

50
00:03:12,337 --> 00:03:12,757
updates.

51
00:03:13,111 --> 00:03:15,111
Commit SHA verification.

52
00:03:15,671 --> 00:03:19,591
So even if a remote branch gets force
pushed or compromised,

53
00:03:20,051 --> 00:03:23,911
the build fails unless the exact commit
SHA matches.

54
00:03:24,571 --> 00:03:26,971
That is real supply chain defense.

55
00:03:27,709 --> 00:03:28,669
Yeah, exactly.

56
00:03:29,289 --> 00:03:34,569
And, uh, speaking of terminal stability,
they also fixed some really annoying TUI

57
00:03:34,629 --> 00:03:37,409
performance bugs that used to freeze up
the interface.

58
00:03:37,759 --> 00:03:38,439
Oh?

59
00:03:38,500 --> 00:03:39,439
What kind of bugs?

60
00:03:39,792 --> 00:03:44,272
Well, PR thirty four seven nine six
addresses large file rendering.

61
00:03:44,512 --> 00:03:50,432
If you ever inspected a minified
JavaScript bundle, a massive SQL dump,

62
00:03:50,485 --> 00:03:54,992
or a huge JSON payload where a single line
exceeded four KiB,

63
00:03:55,032 --> 00:03:58,992
the syntax highlighter would basically
choke and lock up your whole terminal.

64
00:03:59,560 --> 00:04:02,659
Oh, four kilobytes on a single line!

65
00:04:03,279 --> 00:04:06,159
Yeah, minified code will do that every
single time.

66
00:04:06,639 --> 00:04:11,019
It tries to calculate tokens across fifty
thousand characters without a line break

67
00:04:11,059 --> 00:04:12,439
and just melts.

68
00:04:12,833 --> 00:04:13,633
Right!

69
00:04:13,686 --> 00:04:19,633
So now, if a line exceeds four KiB, Codex
automatically bypasses syntax highlighting

70
00:04:19,673 --> 00:04:20,433
for that line.

71
00:04:20,620 --> 00:04:25,073
It just renders the raw text so your
terminal never freezes up.

72
00:04:25,281 --> 00:04:31,793
Plus, in PR thirty four five seven zero,
they added native C plus plus syntax

73
00:04:31,836 --> 00:04:37,233
highlighting for CUDA source files, like
dot cu and dot cuh files.

74
00:04:37,609 --> 00:04:40,730
Oh, CUDA support directly in the TUI!

75
00:04:41,169 --> 00:04:45,269
Machine learning engineers working on GPU
kernels are going to love that.

76
00:04:45,809 --> 00:04:49,429
And did I see something about process
management in the release notes too?

77
00:04:49,792 --> 00:04:52,352
Yeah, PR thirty four six one two.

78
00:04:52,464 --> 00:04:58,592
They fixed background tasks hanging
terminal I O by doing non interactive subprocess

79
00:04:58,752 --> 00:05:00,352
stdin detachment.

80
00:05:00,565 --> 00:05:04,512
So background processes do not block your
input stream anymore.

81
00:05:04,799 --> 00:05:09,539
Man, zero point one four six point zero is
packed.

82
00:05:10,299 --> 00:05:15,059
But, you know, looking at this whole
universal plugin manifest standard across

83
00:05:15,219 --> 00:05:17,539
Bedrock, Claude Code, and Codex...

84
00:05:18,420 --> 00:05:19,460
I am kind of torn.

85
00:05:20,239 --> 00:05:25,180
Part of me wonders if this universal
standard will lead to super bloated multi agent

86
00:05:25,260 --> 00:05:30,500
ecosystems, or if lean, repo local configs
will stay the norm.

87
00:05:30,974 --> 00:05:32,134
That is the tension, right?

88
00:05:32,714 --> 00:05:38,375
Standardizing makes ecosystem expansion
effortless, but repo local plugins checked

89
00:05:38,394 --> 00:05:41,034
into git keep things clean and
predictable.

90
00:05:41,774 --> 00:05:44,274
Time will tell which way engineering teams
lean.

91
00:05:44,652 --> 00:05:50,492
Well, either way, having verified commit
SHAs and a terminal that does not freeze on

92
00:05:50,532 --> 00:05:53,312
four KiB lines makes my day a lot better.

93
00:05:53,972 --> 00:05:54,673
Good chat, Ethan.