1
00:00:00,219 --> 00:00:04,039
Managing custom developer tools across a
whole engineering org,

2
00:00:04,639 --> 00:00:09,739
um, it used to be a total nightmare of
manual repo clones and local folder hacks.

3
00:00:10,439 --> 00:00:14,939
First off, a huge shoutout to Jellypod for
making this daily show possible!

4
00:00:15,599 --> 00:00:20,779
Today we are looking at Codex CLI version
zero point one five three point zero,

5
00:00:21,420 --> 00:00:24,399
which totally changes how we handle plugin
marketplaces.

6
00:00:25,019 --> 00:00:25,579
Yes!

7
00:00:25,980 --> 00:00:31,539
I, I mean, as a former software tester,
state drift with plugins was basically the

8
00:00:31,599 --> 00:00:33,399
bane of my existence.

9
00:00:33,500 --> 00:00:38,079
You think everyone is running the same
setup, and suddenly half the team is on a

10
00:00:38,139 --> 00:00:39,579
broken local fork.

11
00:00:40,036 --> 00:00:40,996
Exactly.

12
00:00:41,076 --> 00:00:46,796
So in zero point one five three point
zero, the CLI adds direct remote marketplace

13
00:00:46,837 --> 00:00:47,316
commands.

14
00:00:47,936 --> 00:00:53,576
You can literally just run codex plugin
list, codex plugin install,

15
00:00:54,076 --> 00:00:58,896
or codex plugin remove, and it queries
remote registry endpoints directly.

16
00:00:59,257 --> 00:01:04,657
Wait, so no more manually cloning plugin
repos into your local codex folder or

17
00:01:04,717 --> 00:01:06,517
pointing to arbitrary file paths?

18
00:01:07,155 --> 00:01:07,714
None at all.

19
00:01:08,254 --> 00:01:12,134
It hits the remote marketplace endpoint,
fetches the catalog,

20
00:01:12,694 --> 00:01:17,774
handles installation, and even formats
remote sources with their version and auth

21
00:01:17,835 --> 00:01:21,095
policies in JSON output if you need to
script it.

22
00:01:21,484 --> 00:01:23,724
That is huge for automation.

23
00:01:24,324 --> 00:01:26,464
But, um, what about security?

24
00:01:26,984 --> 00:01:31,545
If anyone can just pull from a remote
marketplace, doesn't that open up enterprise

25
00:01:31,604 --> 00:01:34,204
environments to unvetted third party code?

26
00:01:34,721 --> 00:01:39,341
That is where pull request four one nine
five three comes in.

27
00:01:39,381 --> 00:01:44,581
They introduced a feature called enforce
marketplace source policy for curated

28
00:01:44,641 --> 00:01:45,142
plugins.

29
00:01:45,821 --> 00:01:51,281
If your enterprise policy mandates curated
sources, the CLI outright blocks

30
00:01:51,321 --> 00:01:56,661
installing non compliant or unverified
remote plugins across team environments.

31
00:01:57,027 --> 00:01:58,347
Oh, I love that.

32
00:01:58,807 --> 00:02:03,047
So admins get governance without locking
down the CLI completely.

33
00:02:03,688 --> 00:02:07,387
And from the testing side, there is
another piece in this release that caught my

34
00:02:07,447 --> 00:02:12,968
eye, pull request four one nine four nine,
app server plugin reconciliation.

35
00:02:13,369 --> 00:02:15,750
How does that work when jumping around
codebases?

36
00:02:16,171 --> 00:02:21,272
So, imagine you are switching between git
feature branches or totally different

37
00:02:21,351 --> 00:02:22,071
project trees.

38
00:02:22,671 --> 00:02:27,252
In the past, active plugin versions could
get out of sync with what the project

39
00:02:27,331 --> 00:02:27,911
expected.

40
00:02:28,672 --> 00:02:34,151
Now, the app server constantly reconciles
installed plugins against the active

41
00:02:34,191 --> 00:02:39,011
environment specs, so your tools stay
consistent without restarting your session

42
00:02:39,111 --> 00:02:40,511
every time you context switch.

43
00:02:40,849 --> 00:02:43,490
That level of predictability makes a huge
difference.

44
00:02:44,149 --> 00:02:49,470
Speaking of making things smoother, let us
talk about latency in zero point one five

45
00:02:49,510 --> 00:02:53,589
three point zero, specifically around
Guardian safety reviews.

46
00:02:53,924 --> 00:02:59,284
Guardian is great for safety, but yeah,
running background checks on every single

47
00:02:59,304 --> 00:03:02,564
turn was definitely adding overhead and
burning tokens.

48
00:03:03,136 --> 00:03:03,336
Right.

49
00:03:03,836 --> 00:03:08,796
So in this release, pull request four two
one four seven changes how Guardian

50
00:03:08,837 --> 00:03:10,676
behaves depending on your approval mode.

51
00:03:11,316 --> 00:03:15,736
If you run in Full Access mode, Guardian
now completely skips review for

52
00:03:15,797 --> 00:03:17,436
confirmation only actions.

53
00:03:17,738 --> 00:03:18,698
Oh, wow!

54
00:03:19,198 --> 00:03:23,878
So if an action does not actually require
explicit user approval anyway,

55
00:03:24,257 --> 00:03:26,237
it does not waste time scoring it?

56
00:03:26,842 --> 00:03:27,803
Exactly.

57
00:03:27,842 --> 00:03:31,142
And if you are in User Approval mode, it
goes even further,

58
00:03:31,602 --> 00:03:35,982
it disables background Guardian scoring
and prewarming entirely.

59
00:03:36,062 --> 00:03:40,503
You still get sensitive action checks and
input prompts, but you drop all that

60
00:03:40,522 --> 00:03:45,943
background overhead, which cuts down turn
latency and saves token consumption big

61
00:03:46,042 --> 00:03:46,202
time.

62
00:03:46,509 --> 00:03:50,149
That is a massive speedup for daily
terminal workflows.

63
00:03:50,809 --> 00:03:53,750
What about configuration updates in config
dot toml?

64
00:03:54,324 --> 00:03:57,244
A couple of nice TUI housekeeping fixes
there.

65
00:03:57,865 --> 00:04:04,604
Pull request four two one zero one lets
you set tui dot auto recap equals false.

66
00:04:05,244 --> 00:04:10,305
That suppresses automatic recaps during
idle turns, though you can still run slash

67
00:04:10,524 --> 00:04:12,764
recap manually whenever you want one.

68
00:04:14,272 --> 00:04:15,392
Thank goodness.

69
00:04:16,053 --> 00:04:20,032
Sometimes you just want your transcript to
stay clean without the agent summarizing

70
00:04:20,052 --> 00:04:21,833
things every time you pause to think.

71
00:04:22,692 --> 00:04:25,532
What happened to the old disable paste
burst setting?

72
00:04:25,891 --> 00:04:31,131
That was moved under the tui table via
pull request four one nine seven six.

73
00:04:31,871 --> 00:04:36,991
It is now tui dot disable paste burst,
though the top level key still works as a

74
00:04:37,051 --> 00:04:39,991
fallback so your existing config won't
break.

75
00:04:40,322 --> 00:04:45,081
And I saw something about usage tracking
for Plus and Team tier accounts?

76
00:04:45,617 --> 00:04:46,037
Yes!

77
00:04:46,678 --> 00:04:52,697
Zero point one five three point zero gives
Plus and Team users an earlier warning

78
00:04:52,737 --> 00:04:57,437
when less than half of their rate
allowance remains inside a five hour usage window.

79
00:04:57,517 --> 00:05:01,937
Instead of surprising you at ninety
percent, it gives you a heads up right at the

80
00:05:01,997 --> 00:05:04,537
fifty percent mark so you can pace your
work.

81
00:05:05,203 --> 00:05:06,982
That is so practical.

82
00:05:07,702 --> 00:05:12,702
When you combine remote marketplace
governance with leaner Guardian approval checks

83
00:05:12,803 --> 00:05:18,022
and earlier rate warnings, you get a much
faster, far more predictable workflow.

84
00:05:18,782 --> 00:05:20,242
Really solid update overall.

85
00:05:20,781 --> 00:05:21,561
Absolutely.

86
00:05:21,981 --> 00:05:26,201
That is our quick take for today, thanks
for listening and see you next time!