1
00:00:00,119 --> 00:00:03,500
Shout out to Jellypod for helping make
this daily show a reality.

2
00:00:04,859 --> 00:00:11,619
So, Maya, OpenAI just dropped Codex
version 0.151.0, and there is a huge

3
00:00:11,779 --> 00:00:16,760
fix in pull request 41208 for anyone
working in a multi repo setup.

4
00:00:17,091 --> 00:00:18,051
Oh yeah!

5
00:00:18,091 --> 00:00:20,231
The plugin catalog issue, right?

6
00:00:20,682 --> 00:00:21,382
Exactly.

7
00:00:21,823 --> 00:00:27,202
If you had five different microservices
open, and one broken repository had an

8
00:00:27,282 --> 00:00:29,843
invalid plugin catalog, it used to...

9
00:00:31,182 --> 00:00:33,722
um, basically choke up the whole
workspace.

10
00:00:34,072 --> 00:00:37,171
It would crash the whole tool resolution
step!

11
00:00:37,811 --> 00:00:38,551
It was awful.

12
00:00:39,351 --> 00:00:44,592
One bad project marketplace JSON file, and
suddenly your global plugins disappear

13
00:00:44,611 --> 00:00:44,931
too.

14
00:00:45,292 --> 00:00:46,092
Right.

15
00:00:46,145 --> 00:00:52,652
So now, Codex 0.151.0 merges your local
dot codex slash

16
00:00:52,742 --> 00:00:58,572
plugins dot toml catalog definitions with
your user level registries in a way that

17
00:00:58,668 --> 00:01:00,252
isolates failures cleanly.

18
00:01:00,649 --> 00:01:03,490
So how does it actually handle the bad
repo now?

19
00:01:03,750 --> 00:01:05,510
It, it, it logs a clear warning.

20
00:01:05,750 --> 00:01:11,350
If a marketplace is unreachable or
corrupt, you get detailed diagnostics when

21
00:01:11,380 --> 00:01:16,790
running codex plugin list with the catalog
flag, or inside your TUI logs.

22
00:01:16,950 --> 00:01:21,430
But all your valid plugins across active
catalogs stay active.

23
00:01:21,836 --> 00:01:27,256
See, coming from a software testing
background, I have mixed feelings about this.

24
00:01:27,436 --> 00:01:33,596
Part of me wants strict validation, like,
fail fast so developers actually fix their

25
00:01:33,636 --> 00:01:35,917
broken configuration files immediately.

26
00:01:36,333 --> 00:01:41,933
Wait, you really want a developer on
another team who broke a config file in repo C

27
00:01:42,093 --> 00:01:45,773
to block me from running my database
plugin in repo A?

28
00:01:47,012 --> 00:01:47,671
Fair point!

29
00:01:48,171 --> 00:01:51,792
When a platform team pushes a bad manifest
on a Friday afternoon,

30
00:01:52,351 --> 00:01:54,951
freezing everyone's dev environment is...

31
00:01:55,271 --> 00:01:56,511
yeah, that is a nightmare.

32
00:01:57,151 --> 00:01:58,591
Resilient fallbacks win here.

33
00:01:59,000 --> 00:02:01,560
It is all about project trust boundaries.

34
00:02:01,720 --> 00:02:07,800
Oh, and by the way, repository level
plugin catalogs only activate once you grant

35
00:02:07,862 --> 00:02:10,520
explicit project trust to that workspace.

36
00:02:10,733 --> 00:02:14,680
So untrusted repos cannot inject tool
registries anyway.

37
00:02:15,007 --> 00:02:16,346
That makes total sense.

38
00:02:16,847 --> 00:02:22,607
So in practice, if I want to set this up,
I define my team tools in dot codex slash

39
00:02:22,766 --> 00:02:28,386
plugins dot toml, and I can verify what is
live using codex plugin status.

40
00:02:28,907 --> 00:02:29,667
Precisely.

41
00:02:30,147 --> 00:02:33,688
Keeps your workspace clean without global
configuration drift.

42
00:02:34,189 --> 00:02:40,389
Speaking of not blocking developer
workflows, let us talk about MCP startup time.

43
00:02:41,089 --> 00:02:47,670
Pull request 41199 adds granular controls
for optional Model Context Protocol

44
00:02:47,769 --> 00:02:48,210
servers.

45
00:02:48,625 --> 00:02:50,705
Ah, the startup grace period setting.

46
00:02:50,845 --> 00:02:57,505
You set mcp optional startup grace ms in
your config dot toml or via the environment

47
00:02:57,567 --> 00:03:01,745
variable CODEX MCP STARTUP GRACE MS.

48
00:03:02,169 --> 00:03:05,509
Why is that so crucial for slow
microservices?

49
00:03:06,042 --> 00:03:11,642
Because optional MCP servers used to hang
the CLI boot sequence if a local service

50
00:03:11,674 --> 00:03:14,042
took, say, three seconds to spin up.

51
00:03:14,242 --> 00:03:20,442
Now, the CLI boots instantly, and Codex
discovers optional tools asynchronously in

52
00:03:20,462 --> 00:03:21,162
the background.

53
00:03:21,447 --> 00:03:23,907
Wait, what if the server is mandatory,
though?

54
00:03:24,208 --> 00:03:25,888
That is the key caveat!

55
00:03:26,012 --> 00:03:31,808
Required MCP servers still enforce a
strict blocking startup check regardless of the

56
00:03:31,861 --> 00:03:32,608
grace setting.

57
00:03:32,724 --> 00:03:35,488
Optional means optional.

58
00:03:35,759 --> 00:03:36,759
Got it.

59
00:03:36,819 --> 00:03:42,239
So mandatory tools fail fast, optional
tools load whenever they are ready.

60
00:03:42,259 --> 00:03:43,179
I like that balance.

61
00:03:43,621 --> 00:03:49,861
There is also a really slick update in
pull request 41206 around mid session model

62
00:03:49,962 --> 00:03:50,361
switching.

63
00:03:51,399 --> 00:03:54,399
What happens when you switch models mid
stream?

64
00:03:54,750 --> 00:03:59,390
Well, if you were using an Ultra reasoning
model with high reasoning effort and you

65
00:03:59,438 --> 00:04:04,270
fall back or switch to a standard
endpoint, the ToolRouter now dynamically

66
00:04:04,377 --> 00:04:09,790
re-evaluates both reasoning effort
parameters and tool availability plans.

67
00:04:10,171 --> 00:04:14,631
So it does not try to pass heavy reasoning
instructions to a model that cannot

68
00:04:14,631 --> 00:04:15,311
process them?

69
00:04:15,667 --> 00:04:16,667
Exactly.

70
00:04:16,734 --> 00:04:19,987
It keeps tool planning correct across
model transitions.

71
00:04:20,299 --> 00:04:26,379
And they also added telemetry for
escalated stdin review size checks in pull request

72
00:04:26,759 --> 00:04:33,479
41189, plus PR 41192 preserves restored
permission profiles

73
00:04:33,619 --> 00:04:35,399
across TUI turn resets.

74
00:04:35,746 --> 00:04:37,606
That permission fix is huge.

75
00:04:38,127 --> 00:04:43,446
Your custom permission profile will not
silently drop back to default restrictions

76
00:04:43,506 --> 00:04:45,146
after a turn reset anymore.

77
00:04:45,856 --> 00:04:50,857
Lots of really solid reliability
engineering in 0.151.0.

78
00:04:51,167 --> 00:04:52,127
Definitely.

79
00:04:52,177 --> 00:04:54,447
Alright, that is the quick rundown for
today.

80
00:04:54,554 --> 00:04:56,047
Catch you all next time!