1
00:00:00,099 --> 00:00:04,519
So, I was, uh, I was working in the shed
last night, trying to get this old trail

2
00:00:04,619 --> 00:00:05,900
bike engine going, right?

3
00:00:06,639 --> 00:00:10,500
And I had my laptop balanced on a milk
crate, updating some dependencies,

4
00:00:10,939 --> 00:00:15,039
and I just- I completely lost my mind with
Claude Code.

5
00:00:15,539 --> 00:00:18,819
Have you ever done a /code-review and
then, like, two prompts later,

6
00:00:18,879 --> 00:00:21,899
the whole tool just feels like it's wading
through thick molasses?

7
00:00:22,522 --> 00:00:23,402
Oh, absolutely.

8
00:00:23,443 --> 00:00:25,422
It's that massive context bloat.

9
00:00:26,002 --> 00:00:29,902
Every single line of that review gets
dumped straight into your active prompt

10
00:00:29,962 --> 00:00:33,062
history, and suddenly you're burning
through tokens like water.

11
00:00:33,125 --> 00:00:33,965
Exactly!

12
00:00:34,032 --> 00:00:36,165
It is a total token hog.

13
00:00:36,305 --> 00:00:42,085
But, mate, they just dropped v2.1.218, and
they've actually fixed this.

14
00:00:42,205 --> 00:00:46,965
Now, when you run /code-review, it spins
up as a background subagent.

15
00:00:47,072 --> 00:00:51,205
It's running on this isolated background
thread, so it doesn't pollute your active

16
00:00:51,254 --> 00:00:52,965
conversation history at all.

17
00:00:53,045 --> 00:00:55,925
Your main terminal prompt stays completely
clean.

18
00:00:56,057 --> 00:00:57,676
Oh, that is huge!

19
00:00:58,196 --> 00:01:01,956
So you don't lose your actual thread of
thought just because you wanted a quick

20
00:01:02,096 --> 00:01:03,536
sanity check on a pull request.

21
00:01:04,076 --> 00:01:09,316
It's like, uh, like delegating the review
to a junior dev in another room instead of

22
00:01:09,396 --> 00:01:12,297
having them stand right over your shoulder
whispering code at you.

23
00:01:12,333 --> 00:01:12,973
Yes!

24
00:01:13,005 --> 00:01:14,893
That is a spot-on way to put it.

25
00:01:15,026 --> 00:01:20,133
It just goes off, does its thing in the
background, and leaves you to keep typing.

26
00:01:20,223 --> 00:01:24,813
But, uh, there's a bit of a catch with
this update if you're big on custom plugins.

27
00:01:24,893 --> 00:01:29,293
They've made a pretty massive breaking
change to how custom skills work,

28
00:01:29,348 --> 00:01:34,413
specifically anything using that context:
fork setup in the YAML frontmatter.

29
00:01:34,516 --> 00:01:36,216
Wait, what kind of change?

30
00:01:36,236 --> 00:01:38,376
Are those skills just running in the
background now too?

31
00:01:38,417 --> 00:01:39,057
Spot on.

32
00:01:39,128 --> 00:01:43,377
Anything with context: fork now defaults
to running in the background.

33
00:01:43,537 --> 00:01:48,337
So, if your custom skill relies on, you
know, asking you questions or expecting

34
00:01:48,384 --> 00:01:52,977
interactive user input mid-flight, it's
just going to hang or run silently.

35
00:01:53,110 --> 00:01:58,017
If you want it to be interactive, you now
have to explicitly go into your YAML and

36
00:01:58,070 --> 00:01:59,697
write background: false.

37
00:01:59,848 --> 00:02:00,067
Huh.

38
00:02:00,687 --> 00:02:05,567
Okay, so it keeps the main loop clean, but
you have to be intentional if you want

39
00:02:05,628 --> 00:02:07,168
that back-and-forth interaction.

40
00:02:07,807 --> 00:02:08,387
That makes sense.

41
00:02:09,107 --> 00:02:12,708
Honestly, though, the thing that caught my
eye in this release is the Windows path

42
00:02:12,807 --> 00:02:13,107
fix.

43
00:02:13,567 --> 00:02:15,847
I mean, did you see the bug with the \u
paths?

44
00:02:16,814 --> 00:02:18,034
Oh, the Unicode thing!

45
00:02:18,534 --> 00:02:19,154
It's classic.

46
00:02:19,634 --> 00:02:25,835
If you had a path like
C:\Users\unicorn-which, let's be honest,

47
00:02:25,894 --> 00:02:30,474
is a pretty common prefix on Windows-the
parser would see that backslash-u and

48
00:02:30,534 --> 00:02:31,654
think, "Ah!

49
00:02:31,975 --> 00:02:33,774
This is a Unicode escape sequence!"

50
00:02:34,354 --> 00:02:38,594
And then it would corrupt the path into
some completely random CJK characters.

51
00:02:39,094 --> 00:02:42,354
Your files would just vanish into a black
hole of unreadability.

52
00:02:43,219 --> 00:02:46,219
"C-Users-unicorn" turned into random
characters.

53
00:02:46,940 --> 00:02:48,119
That is wild.

54
00:02:48,859 --> 00:02:53,079
Imagine trying to debug why your project
suddenly thinks it's living in a completely

55
00:02:53,159 --> 00:02:54,159
different character set.

56
00:02:54,800 --> 00:02:56,179
I'm glad they finally squashed that.

57
00:02:56,799 --> 00:03:00,699
And, oh, they also fixed that infuriating
left-arrow key bug,

58
00:03:00,799 --> 00:03:01,079
right?

59
00:03:01,208 --> 00:03:03,528
Oh, mate, don't get me started on the
left-arrow!

60
00:03:03,648 --> 00:03:07,688
You'd be typing this massive, beautiful,
three-paragraph prompt,

61
00:03:07,708 --> 00:03:12,328
you'd hit the left arrow to go back and
fix a typo, and bam-the whole draft just

62
00:03:12,376 --> 00:03:13,568
gets discarded.

63
00:03:13,640 --> 00:03:14,128
Gone.

64
00:03:14,195 --> 00:03:15,008
Poof.

65
00:03:15,098 --> 00:03:19,528
Now, thank goodness, if you press it after
editing, you actually get a confirmation

66
00:03:19,590 --> 00:03:20,168
dialogue.

67
00:03:20,355 --> 00:03:23,448
It's like a little digital safety net for
your sanity.

68
00:03:23,677 --> 00:03:24,837
Thank goodness.

69
00:03:25,097 --> 00:03:28,757
The amount of times I've accidentally
wiped out a complex prompt because of a quick

70
00:03:28,817 --> 00:03:29,657
navigation edit...

71
00:03:30,317 --> 00:03:30,997
it's painful.

72
00:03:31,678 --> 00:03:33,958
Now, what about the Model Context Protocol
stuff?

73
00:03:34,477 --> 00:03:36,737
I saw some diagnostic updates in the
release notes too.

74
00:03:36,833 --> 00:03:40,033
Yeah, they've really pulled back the
curtain on MCP connections.

75
00:03:40,213 --> 00:03:45,953
Now, when you run claude mcp list or use
the /mcp command, it doesn't just give you

76
00:03:45,993 --> 00:03:47,873
a generic "failed to connect" error.

77
00:03:48,033 --> 00:03:54,593
It actually spits out the raw HTTP status
codes-like a 401 Unauthorized or a 503

78
00:03:54,643 --> 00:03:58,593
Service Unavailable-along with the actual
response body error text.

79
00:03:58,780 --> 00:04:02,993
So you can see exactly why your external
MCP server is throwing a tantrum.

80
00:04:03,159 --> 00:04:07,059
Oh, that's going to make debugging custom
MCP servers so much easier.

81
00:04:07,639 --> 00:04:10,779
No more guessing if it's an auth issue or
if the server is just down.

82
00:04:11,519 --> 00:04:14,300
And didn't they add something about
whitespace in config files too?

83
00:04:14,375 --> 00:04:14,855
They did!

84
00:04:15,095 --> 00:04:18,455
A new linter warning for your
.claude.json.

85
00:04:18,615 --> 00:04:23,175
It flags any invisible leading or trailing
spaces inside your config values.

86
00:04:23,295 --> 00:04:26,775
You wouldn't think a tiny space would
break things, but it's the kind of silent

87
00:04:26,832 --> 00:04:29,255
killer that leads to hours of
head-scratching.

88
00:04:29,629 --> 00:04:30,409
It always is.

89
00:04:31,009 --> 00:04:35,569
Well, it sounds like v2.1.218 is a massive
quality-of-life update,

90
00:04:36,009 --> 00:04:39,109
especially for Windows devs and anyone
running heavy code reviews.

91
00:04:39,689 --> 00:04:40,889
I'm definitely upgrading today.

92
00:04:40,917 --> 00:04:41,957
Yeah, absolutely.

93
00:04:42,197 --> 00:04:46,717
Well, I'm gonna head back out to the shed
and see if I can get this bike started.

94
00:04:46,805 --> 00:04:47,797
Talk soon, mate.

95
00:04:47,792 --> 00:04:48,272
Sounds good.

96
00:04:48,368 --> 00:04:49,632
Good luck with the engine!