1
00:00:00,000 --> 00:00:01,596
G'day everyone, Lachlan Reed here!

2
00:00:01,708 --> 00:00:06,237
Just a quick shout-out to Jellypod for
making this daily show possible.

3
00:00:06,277 --> 00:00:12,476
Now, James, I've got to say, I was messing
around with the new Claude Code v2.1.169

4
00:00:12,545 --> 00:00:17,359
update in my shed last night, and they've
added this new `/cd` command.

5
00:00:17,572 --> 00:00:22,233
It completely saved my bacon while
switching between my frontend and backend repos.

6
00:00:23,000 --> 00:00:26,836
Oh, the `/cd` command is actually huge for
performance.

7
00:00:27,568 --> 00:00:31,078
Before this, if you wanted to switch
directories, you had to spin up a completely

8
00:00:31,158 --> 00:00:32,761
new Claude Code session.

9
00:00:32,873 --> 00:00:36,689
That meant tearing down your terminal
environment and, crucially,

10
00:00:36,733 --> 00:00:38,134
destroying your prompt cache.

11
00:00:38,227 --> 00:00:43,016
Every time you restarted, Claude had to
re-read your entire codebase context from

12
00:00:43,096 --> 00:00:46,695
scratch, costing you serious time and
token overhead.

13
00:00:47,000 --> 00:00:48,677
Ah, the prompt cache!

14
00:00:49,091 --> 00:00:53,386
That explains why my token usage didn't
spike when I jumped from my React native

15
00:00:53,443 --> 00:00:56,426
folder straight into my Go API directory.

16
00:00:56,613 --> 00:00:59,026
It keeps that cache warm in the
background.

17
00:00:59,093 --> 00:01:02,989
It's like not having to reboot your brain
every time you walk into a different room

18
00:01:03,042 --> 00:01:03,710
of the house.

19
00:01:04,000 --> 00:01:04,640
Exactly.

20
00:01:04,667 --> 00:01:05,843
It preserves that state.

21
00:01:05,983 --> 00:01:09,999
Now, speaking of things breaking when you
switch environments,

22
00:01:10,015 --> 00:01:14,958
they also introduced a proper
`--safe-mode` flag, which you can also trigger with

23
00:01:14,998 --> 00:01:19,038
the `CLAUDE_CODE_SAFE_MODE` environment
variable.

24
00:01:20,000 --> 00:01:21,040
Wait, safe mode?

25
00:01:22,047 --> 00:01:24,077
What's that actually turning off under the
hood?

26
00:01:24,370 --> 00:01:30,149
Is it just blocking external API calls, or
is it more like starting a PC in Windows

27
00:01:30,213 --> 00:01:31,029
Safe Mode?

28
00:01:32,000 --> 00:01:34,720
It is very much like Windows Safe Mode.

29
00:01:34,736 --> 00:01:40,399
When you pass `--safe-mode`, Claude Code
completely bypasses any custom plugins,

30
00:01:40,479 --> 00:01:44,720
ignores the instruction rules you've set
up in your `CLAUDE.md` files,

31
00:01:44,740 --> 00:01:48,083
and blocks all custom pre- or
post-execution hooks.

32
00:01:48,270 --> 00:01:52,639
If Claude Code is behaving weirdly or
throwing errors, this lets you instantly

33
00:01:52,719 --> 00:01:57,039
isolate whether it's a bug in the core
tool itself or if one of your custom local

34
00:01:57,099 --> 00:01:58,634
scripts is muckin' things up.

35
00:01:59,000 --> 00:02:00,440
That's brilliant for debugging.

36
00:02:00,720 --> 00:02:06,045
I once spent two hours troubleshooting an
API client wrapper only to realize my own

37
00:02:06,125 --> 00:02:08,277
git hook was breaking the terminal pipe.

38
00:02:09,088 --> 00:02:14,036
Speaking of terminal issues, have you
noticed how much smoother the UI rendering

39
00:02:14,103 --> 00:02:15,241
feels on Mac lately?

40
00:02:16,000 --> 00:02:16,641
Yes!

41
00:02:16,721 --> 00:02:22,161
They finally killed that notorious 30 to
50 millisecond UI rendering lag on macOS.

42
00:02:22,268 --> 00:02:26,799
It used to feel just a tiny bit sluggish
when streaming long responses because the

43
00:02:26,843 --> 00:02:29,429
terminal renderer was choking on stdout.

44
00:02:29,525 --> 00:02:34,155
They've optimized that loop, which
drastically lowered the CPU footprint during

45
00:02:34,212 --> 00:02:35,194
active streaming.

46
00:02:36,000 --> 00:02:40,556
Ah, so that's why my MacBook's fans didn't
sound like a jet engine taking off when I

47
00:02:40,596 --> 00:02:43,194
asked it to refactor a massive utility
file.

48
00:02:44,412 --> 00:02:49,268
And it's not just Mac users getting the
love here; they also patched up a nasty bug

49
00:02:49,295 --> 00:02:53,834
on Windows where running `claude -p` would
just hang indefinitely.

50
00:02:54,000 --> 00:02:58,001
Right, that Windows pipe hang was a real
pain for developers using PowerShell or

51
00:02:58,041 --> 00:02:58,961
command prompts.

52
00:02:59,121 --> 00:03:02,167
On top of that, they've done some serious
enterprise hardening.

53
00:03:02,263 --> 00:03:05,925
They added proper support for
OpenTelemetry client certificates.

54
00:03:06,032 --> 00:03:09,292
So if you're running this inside a
locked-down corporate network that inspects

55
00:03:09,362 --> 00:03:13,770
traffic or requires custom OTEL certs for
logging, it won't block your connection

56
00:03:13,820 --> 00:03:14,250
anymore.

57
00:03:15,000 --> 00:03:17,485
It's great to see them polishing the rough
edges.

58
00:03:17,592 --> 00:03:19,410
It makes me wonder though...

59
00:03:19,619 --> 00:03:24,461
as these CLI tools get more complex with
custom hooks and warm caches,

60
00:03:24,561 --> 00:03:29,578
are we eventually going to need a
full-blown debugger just for our AI terminal

61
00:03:29,629 --> 00:03:30,299
assistants?