1
00:00:00,079 --> 00:00:03,779
So, James, I was, uh, I was hacking away
in my backyard shed last night,

2
00:00:03,899 --> 00:00:08,340
trying to generate this massive PR summary
on a legacy codebase.

3
00:00:08,960 --> 00:00:10,979
And, mate, it absolutely choked.

4
00:00:11,759 --> 00:00:13,099
The terminal just froze.

5
00:00:13,519 --> 00:00:17,399
My keyboard was locked, and I'm sitting
there watching my prompt cache go up in

6
00:00:17,500 --> 00:00:21,279
smoke because the main thread is just
bloated with token history.

7
00:00:21,319 --> 00:00:23,639
It's like trying to pull a caravan with a
pushbike, you know?

8
00:00:24,246 --> 00:00:24,706
Oh, yeah.

9
00:00:25,066 --> 00:00:26,846
The classic terminal lockup.

10
00:00:27,426 --> 00:00:31,766
When you run those deep, multi-step
research tasks directly in your main interactive

11
00:00:31,826 --> 00:00:34,806
thread, it just eats your context window
alive.

12
00:00:35,286 --> 00:00:39,466
It's brutal because you're literally stuck
waiting for the CLI to finish thinking

13
00:00:39,506 --> 00:00:41,226
before you can even type another command.

14
00:00:41,250 --> 00:00:42,050
Exactly!

15
00:00:42,090 --> 00:00:45,010
You're just staring at a flashing cursor,
losing your mind.

16
00:00:45,130 --> 00:00:50,290
But then I looked into the new v2.1.218
release of Claude Code,

17
00:00:50,310 --> 00:00:53,250
and they've completely changed the game
with how they handle skills.

18
00:00:53,318 --> 00:00:56,370
Specifically, this thing called context:
fork.

19
00:00:56,554 --> 00:00:56,914
Yes!

20
00:00:57,214 --> 00:00:59,974
The context: fork update is huge.

21
00:01:00,414 --> 00:01:05,694
In v2.1.218, when you use that parameter,
it now defaults to running your custom

22
00:01:05,795 --> 00:01:06,795
skills in the background.

23
00:01:07,474 --> 00:01:10,774
It basically spawns an isolated,
asynchronous background subagent.

24
00:01:11,255 --> 00:01:15,635
So, you kick off this massive codebase
analysis, it spins up in its own little

25
00:01:15,694 --> 00:01:18,994
bubble, and your active terminal session
stays completely free.

26
00:01:19,654 --> 00:01:23,694
You can keep coding, running tests,
whatever, while the skill is grinding away in

27
00:01:23,715 --> 00:01:24,354
the background.

28
00:01:24,542 --> 00:01:25,822
It's a proper lifesaver.

29
00:01:25,955 --> 00:01:27,422
No more staring at the screen.

30
00:01:27,502 --> 00:01:29,102
And setting it up is dead simple.

31
00:01:29,182 --> 00:01:32,342
You just create a markdown file in your
local directory-like,

32
00:01:32,372 --> 00:01:39,262
say, dot-claude, slash, skills, slash,
test-analyzer.md-and you

33
00:01:39,302 --> 00:01:40,702
write some YAML frontmatter.

34
00:01:40,782 --> 00:01:44,142
You just put context, colon, fork right at
the top.

35
00:01:44,302 --> 00:01:47,302
But, uh, what if you actually want to
watch it work?

36
00:01:47,342 --> 00:01:50,062
Like, you don't want it running in the
background because you need to see the

37
00:01:50,115 --> 00:01:51,662
terminal output live?

38
00:01:51,786 --> 00:01:54,486
Ah, right, if you want to force it back to
the foreground.

39
00:01:55,106 --> 00:01:57,506
They actually relaxed the boolean rules in
this version.

40
00:01:58,046 --> 00:02:01,146
So now, if you want to override that
default background behavior,

41
00:02:01,566 --> 00:02:03,846
you can use loose boolean values in the
frontmatter.

42
00:02:04,386 --> 00:02:07,886
You can literally just write background,
colon, off, or background,

43
00:02:07,946 --> 00:02:11,246
colon, no, to force it to run
synchronously right in front of you.

44
00:02:11,786 --> 00:02:12,986
It's super flexible now.

45
00:02:13,141 --> 00:02:14,581
Right, "off" or "no".

46
00:02:15,341 --> 00:02:20,041
Even a kangaroo could trip over fresh
code, but that makes total sense.

47
00:02:20,121 --> 00:02:22,842
It's much more human-friendly than strict
YAML booleans.

48
00:02:23,581 --> 00:02:27,081
But, hey, there's a pretty massive
security angle to this update too,

49
00:02:27,141 --> 00:02:27,341
right?

50
00:02:28,042 --> 00:02:29,562
Especially around workspace trust?

51
00:02:29,723 --> 00:02:30,683
Oh, absolutely.

52
00:02:31,002 --> 00:02:31,783
This is critical.

53
00:02:32,242 --> 00:02:35,962
Because these custom skills run
automatically based on frontmatter hooks,

54
00:02:36,402 --> 00:02:38,902
there was a real risk of repository
hijacking.

55
00:02:39,543 --> 00:02:43,943
Like, if you git-clone a malicious repo,
and it has a sneaky skill tucked away in

56
00:02:43,963 --> 00:02:47,142
the dot-claude folder, it could run code
without you knowing.

57
00:02:47,923 --> 00:02:54,263
Now, v2.1.218 strictly requires
directory-level workspace trust before any of those

58
00:02:54,343 --> 00:02:58,282
frontmatter hooks will execute inside
untrusted project directories.

59
00:02:59,003 --> 00:03:02,562
If you haven't explicitly trusted that
folder, the skill is blocked.

60
00:03:02,625 --> 00:03:03,265
Too right.

61
00:03:03,385 --> 00:03:07,185
You don't want some rogue script wiping
your hard drive just because you wanted to

62
00:03:07,217 --> 00:03:08,705
look at an open-source project.

63
00:03:08,885 --> 00:03:11,185
And they also tightened up the naming,
didn't they?

64
00:03:11,345 --> 00:03:13,905
No more colons in custom agent names.

65
00:03:14,136 --> 00:03:15,376
Yeah, that's deprecated now.

66
00:03:15,856 --> 00:03:18,536
Colons are strictly reserved for plugin
namespacing.

67
00:03:18,596 --> 00:03:21,696
So if you have old skills with colons in
the name, you'll need to rename them.

68
00:03:22,056 --> 00:03:25,956
It keeps the namespace clean and prevents
conflicts with external MCP servers.

69
00:03:26,000 --> 00:03:30,960
Speaking of MCP, I actually ran into a
weird bug where my tools weren't showing up.

70
00:03:31,280 --> 00:03:36,640
I ran claude mcp list, and it pointed out
this tiny whitespace error in my config

71
00:03:36,704 --> 00:03:37,120
file.

72
00:03:37,413 --> 00:03:42,640
It also has these handy HTTP connection
diagnostics now, which is gold if you're

73
00:03:42,686 --> 00:03:46,800
behind a corporate proxy or just have
dodgy internet like I do out in the shed.

74
00:03:48,051 --> 00:03:50,351
Dodgy internet is the ultimate developer
test.

75
00:03:51,192 --> 00:03:53,151
But yeah, those diagnostics are great.

76
00:03:53,252 --> 00:03:57,351
And while we're on quality-of-life wins,
have you hit the left-arrow key by accident

77
00:03:57,391 --> 00:03:57,472
yet?

78
00:03:58,219 --> 00:03:59,419
Mate, don't get me started.

79
00:04:00,039 --> 00:04:04,559
I used to accidentally delete my entire
terminal input line or history because I was

80
00:04:04,599 --> 00:04:06,899
just trying to move the cursor back to fix
a typo.

81
00:04:07,460 --> 00:04:08,619
It was infuriating.

82
00:04:09,011 --> 00:04:10,152
Well, they fixed that too!

83
00:04:10,691 --> 00:04:14,391
There's now a protective prompt when you
press the left-arrow key directly after

84
00:04:14,491 --> 00:04:14,831
editing.

85
00:04:15,451 --> 00:04:19,331
It basically acts as a safety buffer so
you don't accidentally wipe out your active

86
00:04:19,391 --> 00:04:22,571
conversation history while you're just
trying to navigate your code.

87
00:04:23,191 --> 00:04:26,451
It's a small touch, but man, it saves a
lot of headaches.

88
00:04:26,542 --> 00:04:27,582
It really does.

89
00:04:27,849 --> 00:04:32,142
It's those little things that keep you
sane when you're deep in the zone.

90
00:04:32,382 --> 00:04:39,182
Well, that's v2.1.218 for you-background
subagents, tighter security,

91
00:04:39,222 --> 00:04:41,502
and no more accidental history wipes.

92
00:04:41,862 --> 00:04:45,502
I'm gonna head back to the shed and finish
that PR summary now.

93
00:04:45,662 --> 00:04:47,342
Catch you later, James.

94
00:04:47,333 --> 00:04:48,293
Sounds good, Lachlan.

95
00:04:48,320 --> 00:04:48,853
Go get 'em.