1
00:00:00,099 --> 00:00:05,940
Wait, so if you were developing like two
or three local add ons for a team project,

2
00:00:06,420 --> 00:00:11,119
you used to have to restart your entire
terminal session or point the plugin flag to

3
00:00:11,199 --> 00:00:13,719
just one specific folder at a time, right?

4
00:00:14,049 --> 00:00:15,409
Oh mate, absolutely.

5
00:00:15,869 --> 00:00:19,909
You would be restarting your session
constantly, just throwing away all your prompt

6
00:00:20,029 --> 00:00:23,550
context every single time you wanted to
test a second tool.

7
00:00:24,429 --> 00:00:29,909
But today, brought to you by Jellypod AI,
we are looking at Claude Code version two

8
00:00:30,049 --> 00:00:33,850
point one point two six five, and they
finally fixed that headache.

9
00:00:34,116 --> 00:00:37,336
Yeah, this update changes the whole
workflow for local plugin dev.

10
00:00:37,756 --> 00:00:40,676
Instead of pointing the plugin dir flag at
one single root,

11
00:00:41,076 --> 00:00:44,636
you can now point it at a parent directory
containing a whole bundle of plugin

12
00:00:44,696 --> 00:00:45,056
folders.

13
00:00:45,125 --> 00:00:48,485
Right, so imagine you have a directory
called internal plugins.

14
00:00:48,588 --> 00:00:52,405
Inside it, you have got a database helper,
a deployment script,

15
00:00:52,425 --> 00:00:56,005
and a style checker, each in its own
subfolder with a manifest.

16
00:00:56,105 --> 00:00:59,605
You just pass plugin dir pointing at that
top level folder,

17
00:00:59,645 --> 00:01:03,605
and Claude Code automatically traverses
all those subfolders at launch.

18
00:01:03,704 --> 00:01:08,164
It scans for valid manifest files in each
child folder and mounts every single

19
00:01:08,204 --> 00:01:11,725
detected tool into your active
conversation simultaneously.

20
00:01:12,465 --> 00:01:15,005
But here is the really wild part.

21
00:01:15,944 --> 00:01:18,064
It is not just doing a static check at
startup.

22
00:01:18,125 --> 00:01:18,925
Wait, what do you mean?

23
00:01:19,005 --> 00:01:21,005
It is watching the filesystem?

24
00:01:21,219 --> 00:01:21,919
Exactly.

25
00:01:22,439 --> 00:01:25,319
It actively monitors that target directory
at runtime.

26
00:01:25,819 --> 00:01:30,000
So if you drop a brand new plugin
subfolder into internal plugins while Claude Code

27
00:01:30,039 --> 00:01:34,219
is actively running, or if you delete an
old one, it picks that up live.

28
00:01:34,292 --> 00:01:35,012
Far out.

29
00:01:35,305 --> 00:01:39,972
So it literally mounts or unmounts those
tools live, on the fly,

30
00:01:40,012 --> 00:01:43,972
without killing your running conversation
or blowing away your prompt cache state.

31
00:01:43,958 --> 00:01:44,358
Yep!

32
00:01:44,411 --> 00:01:46,758
No process restarts, no lost history.

33
00:01:46,865 --> 00:01:50,518
It just sees the new manifest and updates
the available tool list mid turn.

34
00:01:50,500 --> 00:01:52,580
That is huge for iterative dev work.

35
00:01:52,683 --> 00:01:57,380
Though, speaking of file scanning, they
did put in a few guardrails for safety,

36
00:01:57,396 --> 00:01:57,780
didn't they?

37
00:01:57,792 --> 00:01:58,512
They did.

38
00:01:58,592 --> 00:02:03,872
If you have complex directory trees or
symlinks, it now explicitly guards against

39
00:02:03,934 --> 00:02:05,472
circular symlink loops.

40
00:02:05,592 --> 00:02:09,792
And if a plugin folder fails to load
because of something like a bad link,

41
00:02:09,859 --> 00:02:14,512
slash plugin will display the exact error
code instead of just silently ignoring the

42
00:02:14,560 --> 00:02:15,872
directory like it used to.

43
00:02:15,994 --> 00:02:17,394
Ah, that is a classic.

44
00:02:17,894 --> 00:02:22,114
Nothing worse than wondering why your
custom tool isn't showing up when it was just

45
00:02:22,134 --> 00:02:24,954
stuck in an infinite loop somewhere down
the path.

46
00:02:24,994 --> 00:02:29,095
And mate, there were a couple of other
really neat quality of life fixes tucked into

47
00:02:29,114 --> 00:02:31,394
two point one point two six five as well,
right?

48
00:02:31,542 --> 00:02:33,542
Yeah, two big ones caught my eye.

49
00:02:33,595 --> 00:02:39,302
First, there is now a hard one gigabyte
disk cap on tool result logs saved to disk.

50
00:02:39,489 --> 00:02:44,342
If a tool output gets truncated because of
that cap, you actually get a clean inline

51
00:02:44,397 --> 00:02:48,502
notification right in the conversation
transcript telling you it was truncated.

52
00:02:48,679 --> 00:02:51,399
Saving our SSDs from runaway log files!

53
00:02:52,079 --> 00:02:54,099
And what about the slash workflows UI?

54
00:02:54,167 --> 00:02:58,007
Oh, the interactive workflows status
display got a great facelift.

55
00:02:58,087 --> 00:03:01,927
Tool calls now show clear status
indicators for running, failed,

56
00:03:01,980 --> 00:03:02,887
or done.

57
00:03:02,947 --> 00:03:07,047
And if a subagent has an active task list,
hitting the Enter key right on that

58
00:03:07,100 --> 00:03:12,487
workflow detail item unfolds all the
nested tool calls with their exact inputs and

59
00:03:12,577 --> 00:03:13,287
outputs.

60
00:03:13,391 --> 00:03:16,331
Pure gold for debugging complex agent
chains.

61
00:03:17,411 --> 00:03:18,731
Well, that wraps up the release!

62
00:03:19,131 --> 00:03:24,092
Upgrade to Claude Code two point one point
two six five, point that plugin dir flag

63
00:03:24,132 --> 00:03:28,172
at your tools folder, and enjoy hot
reloading without losing your context.