1
00:00:00,000 --> 00:00:01,719
Right into the terminal today.

2
00:00:01,839 --> 00:00:08,795
We are looking at Codex CLI version
0.137.0, which dropped on

3
00:00:08,859 --> 00:00:15,193
June 4, 2026, and it has some massive
changes for anyone managing developer

4
00:00:15,236 --> 00:00:20,240
environments at scale -- and thanks to
Jellypod to help make this daily show a

5
00:00:20,310 --> 00:00:20,880
reality.

6
00:00:21,104 --> 00:00:25,195
Maya, the headline for me is programmatic
auditing.

7
00:00:25,339 --> 00:00:29,597
They finally gave us `codex plugin list
--json`.

8
00:00:30,000 --> 00:00:36,740
Finally I mean parsing plain text tables
with awk or grep just to see what plugins

9
00:00:36,740 --> 00:00:43,220
are active in a CI CD pipeline is always a
nightmare Moving to structured JSON is

10
00:00:43,220 --> 00:00:49,479
huge for automation What does the payload
actually look like It is super clean.

11
00:00:49,549 --> 00:00:54,721
You get a root-level array of objects, and
each object contains the plugin name,

12
00:00:54,791 --> 00:01:00,234
version, status, and, crucially, a list of
declared skills and permissions.

13
00:01:00,394 --> 00:01:06,787
This means you can run a bash pipeline
like `codex plugin list --json |

14
00:01:07,187 --> 00:01:13,903
jq '[.[] | select(.status == "active")]'`

15
00:01:14,010 --> 00:01:16,788
to quickly grab only your live
integrations.

16
00:01:17,000 --> 00:01:21,960
Oh that's slick And because it's JSON you
can also audit permissions

17
00:01:21,960 --> 00:01:26,660
programmatically Like if you want to make
sure no local plugin has unauthorized

18
00:01:26,660 --> 00:01:31,720
network access before running an
integration test you can write a pre commit hook to

19
00:01:31,720 --> 00:01:36,740
parse those permission fields But what
happens if you have duplicate plugins Say a

20
00:01:36,740 --> 00:01:41,561
local dev copy and a remote global one
with the same identifier That is where the

21
00:01:41,621 --> 00:01:43,160
new loader updates come in.

22
00:01:43,380 --> 00:01:50,358
Codex 0.137.0 implements a strict
deduplication strategy.

23
00:01:50,598 --> 00:01:55,315
If it detects duplicates between your
local workspace and the global remote

24
00:01:55,386 --> 00:02:00,514
registry, it defaults to the local path
first but flags the duplicate in the

25
00:02:00,558 --> 00:02:01,707
standard error stream.

26
00:02:02,000 --> 00:02:07,840
So it doesn't just crash the execution it
actually lets the process complete but

27
00:02:07,840 --> 00:02:09,877
keeps you informed Exactly.

28
00:02:09,937 --> 00:02:14,035
And they applied that same philosophy to
malformed skills parsing.

29
00:02:14,275 --> 00:02:19,870
In previous versions, if a plugin had a
corrupt or poorly formatted skills schema,

30
00:02:19,910 --> 00:02:22,832
the entire CLI runtime would crash on
startup.

31
00:02:23,032 --> 00:02:28,030
Now, it generates a non-breaking warning,
skips the malformed skill,

32
00:02:28,050 --> 00:02:29,711
and loads the rest of the CLI.

33
00:02:30,000 --> 00:02:36,400
That is a massive relief for anyone
building custom internal tools There is nothing

34
00:02:36,400 --> 00:02:41,080
worse than one developer typo on a custom
schema breaking the terminal for the

35
00:02:41,080 --> 00:02:43,880
entire engineering team Absolutely.

36
00:02:44,040 --> 00:02:48,989
Now, speaking of infrastructure, let's
talk about the remote pairing updates.

37
00:02:49,089 --> 00:02:55,315
Codex has rolled out app-server v2 RPCs,
specifically targetting remote controller

38
00:02:55,384 --> 00:02:56,118
grants.

39
00:02:57,000 --> 00:03:03,660
Wait App Server v2 RPCs What are we
talking about here Managing

40
00:03:03,660 --> 00:03:09,639
local codecs instances from a remote
dashboard or CI controller Precisely.

41
00:03:09,826 --> 00:03:13,955
It lets you programmatically pair a remote
controller with your local running

42
00:03:14,012 --> 00:03:14,434
daemon.

43
00:03:14,581 --> 00:03:20,916
Using the new JSON-RPC endpoints, you can
request a controller grant,

44
00:03:20,980 --> 00:03:26,526
list existing active grants, and revoke
them instantly if a session is compromised.

45
00:03:27,000 --> 00:03:33,020
Okay so if I'm pairing my local dev
machine with a remote pair programming server I

46
00:03:33,020 --> 00:03:39,380
can issue a grant via the CLI and then
revoke it immediately after the session Hmm

47
00:03:39,560 --> 00:03:44,320
that is a lot tighter than leaving open
SSH keys or static tokens lying around

48
00:03:45,000 --> 00:03:50,038
Right, and it uses a challenge-response
handshake to establish that secure channel.

49
00:03:50,305 --> 00:03:54,998
On the user interface side, they also
updated the terminal UI,

50
00:03:55,158 --> 00:03:57,398
or TUI, ergonomics.

51
00:03:57,462 --> 00:04:02,682
They added keybinding support for F13 all
the way through F24.

52
00:04:03,000 --> 00:04:09,840
F13 to F24 who actually has those physical
keys on their keyboard anymore

53
00:04:10,515 --> 00:04:11,363
Physical keys?

54
00:04:11,466 --> 00:04:12,724
Almost nobody.

55
00:04:12,864 --> 00:04:18,483
But power users mapping complex layouts
inside terminal emulators like Kitty or

56
00:04:18,536 --> 00:04:20,718
Alacritty use them constantly.

57
00:04:20,958 --> 00:04:26,393
It allows you to bind highly specific
Codex macros to virtual keys without

58
00:04:26,446 --> 00:04:30,868
conflicting with standard system hotkeys
like F1 or F5.

59
00:04:31,000 --> 00:04:36,580
Ah that makes sense It gives you a clean
slate of hotkeys that won't accidentally

60
00:04:36,580 --> 00:04:41,980
trigger a browser refresh or close your
terminal window What about text input in the

61
00:04:41,980 --> 00:04:45,043
TUI They finally added paste support in
searchable menus!

62
00:04:45,230 --> 00:04:50,889
If you are deep in a TUI menu trying to
paste a 40-character commit hash or a

63
00:04:50,969 --> 00:04:56,330
complex configuration value, you can now
use standard system paste shortcuts.

64
00:04:56,479 --> 00:05:02,104
Before, you had to manually type those
values out, which was just asking for typos.

65
00:05:03,000 --> 00:05:09,920
Oh thank goodness Typoing a long SHA hash
inside a terminal menu is a special

66
00:05:09,920 --> 00:05:15,140
kind of developer frustration This makes
the TUI feel much more like a modern

67
00:05:15,140 --> 00:05:16,959
interface It really does.

68
00:05:17,055 --> 00:05:23,514
That is version 0.137.0 -- robust JSON
auditing for

69
00:05:23,570 --> 00:05:28,555
stability under the hood, and some really
smart quality-of-life updates for power

70
00:05:28,635 --> 00:05:29,911
users in the terminal.

71
00:05:30,000 --> 00:05:35,340
Definitely a release to deploy sooner
rather than later See you next time