1
00:00:01,540 --> 00:00:06,540
So I was messing around with agent tool
approvals earlier, and I swear my index

2
00:00:06,580 --> 00:00:08,580
finger is going to get a workout today.

3
00:00:09,818 --> 00:00:12,118
Wait, you mean the new Touch ID
integration?

4
00:00:13,003 --> 00:00:13,663
Yes!

5
00:00:14,143 --> 00:00:18,403
The, the Codex zero point one five five
point zero release.

6
00:00:18,963 --> 00:00:24,843
According to the OpenAI Codex release
notes, Codex CLI zero point one five five

7
00:00:24,963 --> 00:00:31,243
point zero added Touch ID verification for
MCP requests in local TUI sessions on

8
00:00:31,283 --> 00:00:32,123
supported Macs.

9
00:00:32,680 --> 00:00:37,440
Right, because previously, if you were
running Model Context Protocol servers for,

10
00:00:37,560 --> 00:00:42,460
say, production database connectors or
cloud deployments, you were stuck in this

11
00:00:42,560 --> 00:00:43,340
awful dilemma.

12
00:00:43,960 --> 00:00:49,520
You either passed scary auto approval
flags or you typed yes fifty times a minute.

13
00:00:49,682 --> 00:00:50,882
Exact, exactly.

14
00:00:51,522 --> 00:00:52,942
Prompt fatigue is real.

15
00:00:53,422 --> 00:00:58,422
People end up just broad approving
everything because typing y and pressing enter

16
00:00:58,522 --> 00:01:00,682
over and over breaks your whole flow.

17
00:01:01,422 --> 00:01:05,562
But now, when an MCP tool wants to execute
something high privilege,

18
00:01:06,042 --> 00:01:09,262
the app server triggers a native macOS
prompt.

19
00:01:09,625 --> 00:01:11,785
And it is not just a UI trick either.

20
00:01:11,972 --> 00:01:17,305
It actually signs the approval payload
using the Secure Enclave on the Mac hardware.

21
00:01:17,449 --> 00:01:23,065
That is pulled from pull requests forty
three six two four and forty three seven one

22
00:01:23,145 --> 00:01:23,545
two.

23
00:01:23,943 --> 00:01:27,243
Wait, how does it handle switching between
projects?

24
00:01:27,763 --> 00:01:32,383
Like, if I have an administrative tool
open in one window and some random third

25
00:01:32,483 --> 00:01:33,943
party repo open in another?

26
00:01:34,500 --> 00:01:35,900
That is the smart part.

27
00:01:35,972 --> 00:01:39,220
They added workspace scoped identity
protection.

28
00:01:39,396 --> 00:01:44,820
User verification providers now pin
identity to the active workspace root.

29
00:01:44,873 --> 00:01:50,660
So a rogue prompt or bad actor in an
untrusted project directory cannot tap into the

30
00:01:50,717 --> 00:01:53,540
authorization state you granted somewhere
else.

31
00:01:53,922 --> 00:01:58,782
Okay, but what happens when I tap cancel
because I realize the agent is about to

32
00:01:58,842 --> 00:01:59,662
drop a schema?

33
00:02:00,202 --> 00:02:01,482
Does the whole turn crash?

34
00:02:01,875 --> 00:02:04,675
No, it handles RPC cancellation cleanly.

35
00:02:04,812 --> 00:02:10,355
Canceling the Touch ID prompt sends a
cancel signal back to the app server without

36
00:02:10,399 --> 00:02:11,875
dropping your thread context.

37
00:02:12,035 --> 00:02:17,795
Plus, they adjusted the Guardian score
policy so the extra biometric check step does

38
00:02:17,875 --> 00:02:20,595
not falsely drag down turn performance
numbers.

39
00:02:20,985 --> 00:02:23,065
That is actually really smooth.

40
00:02:23,565 --> 00:02:27,705
It turns what used to be a friction point
into a quick physical tap.

41
00:02:28,042 --> 00:02:33,802
Now, speaking of workflow friction, the
zero point one five five point zero release

42
00:02:33,930 --> 00:02:37,002
also fixes a big headache with background
daemons.

43
00:02:37,362 --> 00:02:39,562
Oh man, the background restarts?

44
00:02:40,462 --> 00:02:45,562
I used to have active subagents just lose
their mind mid task if the background

45
00:02:45,602 --> 00:02:46,562
process updated.

46
00:02:46,875 --> 00:02:47,835
Exactly.

47
00:02:47,899 --> 00:02:52,795
They added configurable daemon update
schedules and a explicit command,

48
00:02:52,855 --> 00:02:54,875
codex app server daemon update.

49
00:02:55,035 --> 00:03:00,155
The best part is that saved threads and
active session goals can now recover right

50
00:03:00,208 --> 00:03:01,595
after the daemon restarts.

51
00:03:01,925 --> 00:03:04,805
That is huge for long running tasks!

52
00:03:05,425 --> 00:03:07,045
What about in the TUI itself?

53
00:03:07,345 --> 00:03:10,605
Anything new to look at while the model is
deep in thought?

54
00:03:11,000 --> 00:03:14,680
Instead of just staring at a static
spinning wheel for thirty seconds,

55
00:03:14,720 --> 00:03:18,760
the status row now streams live reasoning
summaries in real time.

56
00:03:18,920 --> 00:03:24,360
And once a turn finishes, it prints
explicit completion timestamps right there.

57
00:03:25,495 --> 00:03:29,975
No more guessing whether it finished two
seconds ago or ten minutes ago while I was

58
00:03:30,015 --> 00:03:30,915
grabbing coffee.

59
00:03:31,333 --> 00:03:32,133
Right.

60
00:03:32,173 --> 00:03:36,133
And for people managing multiple agents
across repositories,

61
00:03:36,173 --> 00:03:39,893
the agents overview now shows worktree
ownership details.

62
00:03:40,033 --> 00:03:46,373
You can hide, archive, or delete
background tasks, and confirmed deletion actually

63
00:03:46,430 --> 00:03:51,093
cleans up managed git worktrees so you do
not accumulate orphan folders.

64
00:03:51,645 --> 00:03:53,725
That keeps your local workspace clean.

65
00:03:54,485 --> 00:03:56,785
Did they touch provider authentications
too?

66
00:03:57,405 --> 00:03:59,285
I saw something about Amazon Bedrock.

67
00:03:59,708 --> 00:04:05,468
Yeah, Bedrock can now grab AWS credentials
directly from configured shell commands,

68
00:04:05,512 --> 00:04:08,988
complete with expiration caching and
automatic refresh.

69
00:04:09,380 --> 00:04:12,700
Oh, and we cannot forget the experimental
voice feature!

70
00:04:13,240 --> 00:04:20,120
If you pass slash experimental, you can
try live slash voice WebRTC conversations

71
00:04:20,520 --> 00:04:25,180
with live split flap animated transcript
tiles right inside the terminal.

72
00:04:26,580 --> 00:04:29,040
Split flap animation in a terminal UI?

73
00:04:29,680 --> 00:04:32,900
That is equal parts retro and ridiculously
cool.

74
00:04:33,558 --> 00:04:34,598
It really is.

75
00:04:35,178 --> 00:04:37,098
Sounds like a solid release all around.

76
00:04:37,578 --> 00:04:39,038
Good stuff to play with today!