1
00:00:00,140 --> 00:00:01,500
Okay, picture this.

2
00:00:02,260 --> 00:00:05,760
A container build is running at two in the
morning, nobody's awake,

3
00:00:06,320 --> 00:00:08,620
and it needs a plugin that wants an API
key.

4
00:00:09,440 --> 00:00:10,320
Where does the key go?

5
00:00:11,042 --> 00:00:12,082
Right, that's the wall.

6
00:00:12,229 --> 00:00:14,482
Until now the answer was a menu.

7
00:00:14,602 --> 00:00:18,802
You'd open /plugin, go to Configure, and
type it in by hand.

8
00:00:18,833 --> 00:00:20,473
In a Dockerfile.

9
00:00:20,593 --> 00:00:23,713
Mate, that's like asking a fridge to fill
out a form.

10
00:00:24,410 --> 00:00:24,950
Pretty much.

11
00:00:25,530 --> 00:00:28,730
But the 2.1.285 changelog says that's
changed.

12
00:00:29,150 --> 00:00:32,510
You can now set a bundled server's own
settings at install time,

13
00:00:32,910 --> 00:00:35,410
so it starts without you visiting that
Configure screen.

14
00:00:35,538 --> 00:00:38,678
Quick word first, this one's brought to
you by Jellypod AI.

15
00:00:39,998 --> 00:00:40,278
Right.

16
00:00:41,318 --> 00:00:42,298
Bundled server.

17
00:00:43,478 --> 00:00:44,558
What's that, exactly?

18
00:00:45,708 --> 00:00:52,428
It's an MCP server packaged inside a
plugin, in a file format called dot mcpb.

19
00:00:52,548 --> 00:00:55,708
And the install command takes the config
flag now.

20
00:00:55,788 --> 00:01:01,308
You write the server name, a dot, the key,
an equals sign, and the value.

21
00:01:01,333 --> 00:01:07,093
So it's like, um, server dot key equals
value.

22
00:01:07,333 --> 00:01:09,813
Just stuck on the end of the install.

23
00:01:10,000 --> 00:01:10,320
Yep.

24
00:01:10,360 --> 00:01:11,600
One line, no menu.

25
00:01:11,745 --> 00:01:14,185
But how do I know what keys a plugin even
wants?

26
00:01:14,785 --> 00:01:18,485
I'd be guessing, and guessing at two in
the morning is how I nearly wrecked a

27
00:01:18,525 --> 00:01:19,505
client's site once.

28
00:01:19,625 --> 00:01:20,585
That's the second piece.

29
00:01:20,705 --> 00:01:24,825
The changelog says claude plugin
configure, then the plugin name,

30
00:01:24,918 --> 00:01:28,105
shows the plugin's options and which ones
are unset.

31
00:01:28,345 --> 00:01:31,945
So you run it, see the gaps, and fill
exactly those.

32
00:01:32,042 --> 00:01:34,282
Like a checklist that tells you what you
forgot.

33
00:01:34,292 --> 00:01:34,772
Right.

34
00:01:34,792 --> 00:01:36,372
And it can also save values.

35
00:01:36,452 --> 00:01:41,252
The changelog says it reads them from
stdin, with the values stdin flag.

36
00:01:41,392 --> 00:01:41,772
Hmm.

37
00:01:42,652 --> 00:01:45,812
Why's stdin better than just typing the
value in the command?

38
00:01:46,195 --> 00:01:49,855
That part's my inference, not the
changelog's, so take it with a grain of salt.

39
00:01:50,435 --> 00:01:53,655
But anything you type as an argument can
land in shell history,

40
00:01:54,135 --> 00:01:55,635
or show up in a process list.

41
00:01:56,155 --> 00:01:59,415
Piping it in, from a secrets manager say,
dodges both.

42
00:01:59,500 --> 00:01:59,980
Huh.

43
00:02:00,247 --> 00:02:03,820
So the secret goes down a pipe instead of
on the whiteboard.

44
00:02:04,273 --> 00:02:04,973
I'm stealing that.

45
00:02:05,458 --> 00:02:06,498
Now the sneaky bit.

46
00:02:06,658 --> 00:02:08,818
What was the bug they fixed?

47
00:02:08,833 --> 00:02:10,033
Oh, this one's nasty.

48
00:02:10,173 --> 00:02:15,313
The changelog says plugins were silently
skipping a bundled dot mcpb server that

49
00:02:15,353 --> 00:02:16,753
still needed configuration.

50
00:02:16,953 --> 00:02:18,153
Silently.

51
00:02:18,273 --> 00:02:18,993
No warning.

52
00:02:19,000 --> 00:02:22,680
So the pipeline goes green, and your tool
just isn't there.

53
00:02:22,708 --> 00:02:24,068
Exactly the trap.

54
00:02:24,208 --> 00:02:29,268
Now /plugin, the install message, and the
install command all say so,

55
00:02:29,308 --> 00:02:31,348
and point you to Configure.

56
00:02:31,515 --> 00:02:31,795
Good.

57
00:02:32,195 --> 00:02:34,735
A loud failure beats a quiet one every
time.

58
00:02:34,833 --> 00:02:37,393
And there's an SSH fix in the same
release.

59
00:02:37,496 --> 00:02:42,913
Plugin and marketplace installs over SSH
were ignoring the ssh program set in GIT

60
00:02:43,073 --> 00:02:47,473
SSH, or in your git config's core dot
sshCommand.

61
00:02:47,500 --> 00:02:51,740
So if I had a custom key set up, it just,
it just went and used the default one?

62
00:02:51,750 --> 00:02:53,350
Basically, it ignored your program.

63
00:02:53,530 --> 00:02:54,870
Now it respects it.

64
00:02:54,875 --> 00:02:55,835
Fair.

65
00:02:55,897 --> 00:02:57,435
Anything else worth grabbing?

66
00:02:57,458 --> 00:02:58,418
Three small ones.

67
00:02:58,525 --> 00:03:02,898
First, an environment variable, CLAUDE
CODE DISABLE WEB FETCH,

68
00:03:02,991 --> 00:03:04,498
turns off the WebFetch tool.

69
00:03:04,631 --> 00:03:07,058
Handy if a runner shouldn't be touching
the network.

70
00:03:07,083 --> 00:03:08,603
Lock the door from the inside.

71
00:03:08,625 --> 00:03:13,425
Second, background Bash and PowerShell
commands now stop after a time limit.

72
00:03:13,515 --> 00:03:18,945
Default is 30 minutes, max is 2 hours, and
Claude gets notified when one is stopped.

73
00:03:19,138 --> 00:03:20,478
Oh, that's the zombie killer.

74
00:03:21,418 --> 00:03:23,658
I've left a dodgy process running
overnight before.

75
00:03:24,518 --> 00:03:25,018
Not proud.

76
00:03:26,140 --> 00:03:31,200
And third, claude with the desktop flag
opens the Claude desktop app on your current

77
00:03:31,280 --> 00:03:31,820
directory.

78
00:03:32,340 --> 00:03:35,140
Or on a session, if you add continue or
resume with an ID.

79
00:03:35,292 --> 00:03:37,372
So terminal to desktop, same spot.

80
00:03:37,375 --> 00:03:38,255
Yep.

81
00:03:38,292 --> 00:03:39,612
Okay, so the two a.m.

82
00:03:39,645 --> 00:03:39,892
build.

83
00:03:39,996 --> 00:03:45,732
Configure command shows the gaps, install
with server dot key equals value fills

84
00:03:45,764 --> 00:03:50,692
them, secrets come down the pipe, and if
something's missing it actually yells.

85
00:03:50,708 --> 00:03:51,108
That's it.

86
00:03:51,154 --> 00:03:52,308
Nobody has to be awake.

