1
00:00:00,000 --> 00:00:01,520
G'day everyone, welcome to the show!

2
00:00:01,760 --> 00:00:04,640
I'm Lachlan Reed, and I'm joined by James
Turner.

3
00:00:04,660 --> 00:00:09,761
And James, if you've ever spent ten
minutes hunting down a hidden JSON configuration

4
00:00:09,905 --> 00:00:15,121
file just to toggle a single setting in
your CLI tool, you are going to love this

5
00:00:15,178 --> 00:00:15,761
update.

6
00:00:15,864 --> 00:00:21,361
Claude Code version 2.1.181 is out, and
they've finally killed the

7
00:00:21,441 --> 00:00:23,761
"edit-config-and-restart" loop.

8
00:00:24,000 --> 00:00:25,200
Oh, thank goodness.

9
00:00:25,872 --> 00:00:28,320
That loop is the ultimate flow-state
killer.

10
00:00:28,432 --> 00:00:29,920
What did they replace it with?

11
00:00:30,000 --> 00:00:36,000
They introduced a beautiful, on-the-fly
`/config key=value` syntax.

12
00:00:36,180 --> 00:00:40,560
You can type it directly into your active
prompt session, or even pass it through

13
00:00:40,600 --> 00:00:43,280
one-off commands using the `-p` flag.

14
00:00:43,547 --> 00:00:46,960
No config files, no restarting the
session.

15
00:00:47,067 --> 00:00:48,720
It just works.

16
00:00:49,000 --> 00:00:52,120
Wait, so I can change behavior
mid-session?

17
00:00:52,824 --> 00:00:54,040
Give me a concrete example.

18
00:00:54,072 --> 00:00:56,600
What's a setting we can actually toggle on
the fly now?

19
00:00:57,000 --> 00:01:01,480
Alright, absolute classic use case:
Claude's extended thinking.

20
00:01:01,568 --> 00:01:05,640
Sometimes you want deep reasoning, but
other times you're just doing basic

21
00:01:05,720 --> 00:01:07,400
refactoring and want speed.

22
00:01:07,560 --> 00:01:12,520
Now, you just type `/config
thinking=false` right there in the prompt,

23
00:01:12,600 --> 00:01:15,880
and boom-latency is cut in half for the
next turn.

24
00:01:16,000 --> 00:01:16,880
No way.

25
00:01:17,552 --> 00:01:19,840
That is huge for rapid-fire debugging.

26
00:01:19,960 --> 00:01:23,280
You don't want to wait for a giant
reasoning chain when you're just asking it to fix

27
00:01:23,360 --> 00:01:25,840
a typo or rename a variable.

28
00:01:25,920 --> 00:01:28,160
And you said this works with Remote
Control mode too?

29
00:01:29,000 --> 00:01:29,720
Spot on.

30
00:01:29,827 --> 00:01:34,200
If you're driving Claude Code remotely via
an API or an external script,

31
00:01:34,240 --> 00:01:37,960
you can pipe that `/config` command
straight through to adjust parameters

32
00:01:38,020 --> 00:01:40,440
dynamically based on the task complexity.

33
00:01:40,627 --> 00:01:43,960
It makes the whole execution pipeline
incredibly flexible.

34
00:01:44,000 --> 00:01:45,440
That's incredibly slick.

35
00:01:46,206 --> 00:01:49,286
Now, what about the other under-the-hood
stuff in this release?

36
00:01:49,526 --> 00:01:51,366
I saw something about a presence file?

37
00:01:52,000 --> 00:01:52,560
Yes!

38
00:01:53,008 --> 00:01:56,480
This one is a massive quality-of-life win
if you use the mobile app alongside the

39
00:01:56,600 --> 00:01:57,120
CLI.

40
00:01:57,248 --> 00:02:01,760
They've added an environment variable
called `CLAUDE_CLIENT_PRESENCE_FILE`.

41
00:02:01,847 --> 00:02:05,920
Essentially, it writes a temporary file to
track when you are actively typing in

42
00:02:05,952 --> 00:02:06,800
your terminal.

43
00:02:07,000 --> 00:02:07,320
Ah!

44
00:02:07,545 --> 00:02:11,320
Let me guess-so it knows you're at your
desk and stops buzzing your phone with

45
00:02:11,376 --> 00:02:13,240
duplicate push notifications?

46
00:02:14,000 --> 00:02:14,960
Exactly!

47
00:02:15,627 --> 00:02:18,720
No more pocket vibrations every time you
run a query.

48
00:02:18,827 --> 00:02:22,880
It silences those mobile notifications
while you're active on the desktop client.

49
00:02:23,040 --> 00:02:25,920
It's a tiny detail, but it saves your
sanity.

50
00:02:26,000 --> 00:02:29,840
Honestly, those are the details that show
they're actually using their own tool.

51
00:02:30,000 --> 00:02:32,000
What about macOS users?

52
00:02:32,280 --> 00:02:34,160
I heard there's a new sandbox tweak.

53
00:02:35,000 --> 00:02:35,880
Spot on, mate.

54
00:02:35,960 --> 00:02:40,040
They introduced a new toggle called
`sandbox.allowAppleEvents`.

55
00:02:40,110 --> 00:02:44,200
Because Claude Code runs in a secure
sandbox, it used to block AppleScript and

56
00:02:44,246 --> 00:02:45,720
system events entirely.

57
00:02:45,840 --> 00:02:50,120
Now, if you toggle this to true, Claude
can actually send Apple Events to automate

58
00:02:50,160 --> 00:02:51,640
other macOS apps.

59
00:02:52,000 --> 00:02:52,639
Oh, wow.

60
00:02:52,746 --> 00:02:56,770
That sounds incredibly powerful but also
slightly terrifying.

61
00:02:56,833 --> 00:02:59,450
Claude scripting my actual operating
system?

62
00:03:00,400 --> 00:03:02,760
Yeah, it definitely raises the stakes.

63
00:03:02,890 --> 00:03:07,120
But for developers trying to build local
automation workflows,

64
00:03:07,147 --> 00:03:08,800
it opens up a whole new world.

65
00:03:08,944 --> 00:03:10,400
Just...

66
00:03:10,467 --> 00:03:14,560
maybe watch what you approve when the
permission prompts start popping up!

67
00:03:15,000 --> 00:03:15,720
Fair enough!

68
00:03:16,237 --> 00:03:21,240
Keep your guard rails up, but definitely
grab version 2.1.181.

69
00:03:21,336 --> 00:03:24,760
That `/config` command alone is worth the
update.

70
00:03:25,000 --> 00:03:26,040
Absolutely.

71
00:03:26,104 --> 00:03:29,240
That's our quick look at the latest Claude
Code update.

72
00:03:29,373 --> 00:03:32,440
Go update your packages, and we'll catch
you in the next one!