1
00:00:00,159 --> 00:00:03,099
I was setting up an automated dev
container setup the other night,

2
00:00:03,179 --> 00:00:06,219
right, and the whole build just completely
froze.

3
00:00:06,299 --> 00:00:11,340
A third party Sentry MCP server popped up
demanding an interactive menu prompt right

4
00:00:11,359 --> 00:00:12,639
in the middle of a headless script.

5
00:00:14,119 --> 00:00:15,559
Stalled the entire pipeline.

6
00:00:16,662 --> 00:00:20,322
Ah, the classic interactive prompt trap in
a headless environment.

7
00:00:21,023 --> 00:00:25,622
But, speaking of smooth builds, this
episode is brought to you by Jellypod AI,

8
00:00:26,003 --> 00:00:30,142
the best way to turn your written content
into natural audio podcasts.

9
00:00:30,427 --> 00:00:31,067
Spot on.

10
00:00:31,347 --> 00:00:35,088
And luckily, Claude Code version two point
one point one hundred and eighty six

11
00:00:35,608 --> 00:00:37,107
completely fixes that headache.

12
00:00:37,387 --> 00:00:42,027
They added standalone CLI commands to
authenticate a configured MCP server from your

13
00:00:42,067 --> 00:00:44,967
shell without ever launching an
interactive session.

14
00:00:45,447 --> 00:00:47,506
Yeah, this is huge for automation!

15
00:00:47,926 --> 00:00:53,986
Now you can literally just run claude mcp
login sentry or claude mcp logout sentry

16
00:00:54,047 --> 00:00:57,007
directly inside your Bash or zsh scripts.

17
00:00:57,766 --> 00:01:00,547
It triggers the OAuth browser flow right
from the command line,

18
00:01:00,966 --> 00:01:02,966
no manual menu navigation required.

19
00:01:03,099 --> 00:01:08,079
So if you are bootstrapping a fresh cloud
environment or resetting credentials

20
00:01:08,159 --> 00:01:12,619
across a dev team, you can just wrap those
commands in a script and walk away to

21
00:01:12,659 --> 00:01:13,260
grab a cuppa.

22
00:01:13,473 --> 00:01:14,032
Exactly.

23
00:01:14,492 --> 00:01:18,293
And that is not the only shell improvement
in version two point one point one

24
00:01:18,392 --> 00:01:19,333
hundred and eighty six.

25
00:01:20,032 --> 00:01:22,812
They also tweaked the exclamation point
prefix behavior.

26
00:01:23,412 --> 00:01:27,833
If you run something like exclamation
point npm test, the terminal output passes

27
00:01:27,892 --> 00:01:30,333
directly to Claude for instant failure
analysis.

28
00:01:30,574 --> 00:01:35,074
Wait, so if my test suite throws a wobbly,
Claude catches the standard output right

29
00:01:35,174 --> 00:01:35,394
away?

30
00:01:35,974 --> 00:01:39,615
What if I do not want Claude automatically
reading every single terminal response

31
00:01:39,654 --> 00:01:39,795
though?

32
00:01:39,974 --> 00:01:40,794
You can turn it off!

33
00:01:41,294 --> 00:01:45,114
Just set respondToBashCommands to false in
your settings dot json file.

34
00:01:45,154 --> 00:01:47,594
It gives you full control over when Claude
intervenes.

35
00:01:47,744 --> 00:01:48,884
Ah, fair dinkum.

36
00:01:49,264 --> 00:01:50,244
And what about security?

37
00:01:50,484 --> 00:01:54,625
Because if Claude is executing terminal
commands, I would be a bit nervous about

38
00:01:54,664 --> 00:01:57,104
sandboxed tools snooping around my local
machine.

39
00:01:57,324 --> 00:01:58,304
They thought of that too.

40
00:01:58,904 --> 00:02:03,804
There is a new sandbox dot credentials
rule that explicitly locks down sandboxed CLI

41
00:02:03,864 --> 00:02:04,684
tools.

42
00:02:04,744 --> 00:02:09,524
It stops them from harvesting your local
API keys or SSH keys while running commands

43
00:02:09,545 --> 00:02:10,364
in the sandbox.

44
00:02:11,296 --> 00:02:12,897
Oh, that is a massive relief.

45
00:02:13,756 --> 00:02:17,196
Though, I did hit a tiny snag when testing
remote dev boxes.

46
00:02:17,636 --> 00:02:22,476
If you run claude mcp login on a remote
machine, you gotta make sure your local

47
00:02:22,536 --> 00:02:27,136
browser callback ports are properly
forwarded, or the OAuth redirect just spins

48
00:02:27,216 --> 00:02:27,616
forever.

49
00:02:28,011 --> 00:02:29,571
Right, port forwarding is key there.

50
00:02:30,071 --> 00:02:33,751
Also, keep in mind how token retention
works across session resets.

51
00:02:34,391 --> 00:02:38,092
Oh, and if you ever accidentally wipe your
context with a forward slash clear

52
00:02:38,132 --> 00:02:42,391
command, you can use forward slash rewind
to recover your session history!

53
00:02:43,716 --> 00:02:47,956
Mate, forward slash rewind has saved my
bacon more times than I care to admit.

54
00:02:49,156 --> 00:02:51,217
Alright, that is the quick fix for today.

55
00:02:51,616 --> 00:02:52,616
Happy coding, everyone.