1
00:00:00,000 --> 00:00:01,120
Welcome to the show, everyone!

2
00:00:01,280 --> 00:00:05,600
I'm Lachlan Reed, here with James Turner,
and today's episode is brought to you by

3
00:00:05,680 --> 00:00:06,880
Jellypod AI.

4
00:00:07,060 --> 00:00:12,242
Now, James, picture this: you're sitting
at your desk, absolutely in the zone,

5
00:00:12,292 --> 00:00:13,682
staring at your monitor.

6
00:00:13,780 --> 00:00:18,162
Suddenly, your thigh starts buzzing like a
trapped hornet because your phone is

7
00:00:18,202 --> 00:00:23,042
going mental with push notifications about
the exact terminal task you're already

8
00:00:23,086 --> 00:00:24,162
watching on your screen.

9
00:00:25,095 --> 00:00:27,682
It's enough to make you throw your phone
out the window!

10
00:00:28,000 --> 00:00:29,360
Oh, I know that pain.

11
00:00:29,860 --> 00:00:33,600
You're using Claude Code's Remote Control
to monitor some massive,

12
00:00:33,667 --> 00:00:37,440
multi-hour build, which is fantastic when
you're getting a coffee,

13
00:00:37,460 --> 00:00:40,160
but a total distraction nightmare when
you're actively sitting there.

14
00:00:40,293 --> 00:00:42,320
It's like your terminal is screaming "Hey!

15
00:00:42,384 --> 00:00:43,440
Look at me!"

16
00:00:43,467 --> 00:00:45,120
while you are literally looking at it.

17
00:00:46,000 --> 00:00:46,880
Exactly!

18
00:00:47,107 --> 00:00:48,720
It's a proper head-scratcher.

19
00:00:48,920 --> 00:00:53,280
But the folks behind Claude Code must have
felt our pain, because in version

20
00:00:53,440 --> 00:00:58,960
2.1.181, they've introduced this clever
little environment variable called

21
00:00:59,080 --> 00:01:01,440
`CLAUDE_CLIENT_PRESENCE_FILE`.

22
00:01:01,733 --> 00:01:06,400
It basically acts like a digital "do not
disturb" sign for your phone when you're at

23
00:01:06,416 --> 00:01:06,960
your desk.

24
00:01:07,000 --> 00:01:09,160
Okay, so how does it actually know you're
there?

25
00:01:09,293 --> 00:01:13,720
Is it running some heavy background daemon
that's constantly eating up CPU cycles to

26
00:01:13,768 --> 00:01:15,000
poll your system status?

27
00:01:15,000 --> 00:01:17,880
Nah, mate, they've gone for a beautiful,
lightweight approach.

28
00:01:17,933 --> 00:01:19,480
No polling at all.

29
00:01:19,540 --> 00:01:24,280
Instead, Claude Code checks for the
existence of this specific marker file

30
00:01:24,387 --> 00:01:25,560
on-demand.

31
00:01:25,576 --> 00:01:29,960
When a notification-triggering event
happens, it quickly glances to see if that file

32
00:01:30,051 --> 00:01:30,680
exists.

33
00:01:30,867 --> 00:01:35,800
If it does, it assumes you're at your
computer and silences the mobile push.

34
00:01:35,987 --> 00:01:41,640
It's brilliant-zero CPU overhead, taming
the beast without melting your laptop.

35
00:01:42,000 --> 00:01:43,920
Ah, that's incredibly elegant.

36
00:01:44,707 --> 00:01:49,205
So the presence file itself is just a
dummy file, and we get to decide how to create

37
00:01:49,245 --> 00:01:50,005
and destroy it.

38
00:01:50,218 --> 00:01:54,725
To implement this, you'd just export
`CLAUDE_CLIENT_PRESENCE_FILE` pointing to a

39
00:01:54,765 --> 00:01:58,445
temporary path, like
`/tmp/claude_present`.

40
00:01:58,505 --> 00:02:01,925
But then how do we automate the locking
mechanism?

41
00:02:02,000 --> 00:02:02,720
Spot on!

42
00:02:02,840 --> 00:02:06,000
You just wire it up to your OS screen-lock
events.

43
00:02:06,187 --> 00:02:10,401
If you're on a Mac, you can write a tiny
Hammerspoon script to watch for when your

44
00:02:10,458 --> 00:02:14,001
screen unlocks, which then touches the
file to create it.

45
00:02:14,113 --> 00:02:17,521
When you lock up and walk away,
Hammerspoon deletes it.

46
00:02:17,708 --> 00:02:21,921
If you're on Linux, you can do the exact
same thing using a `dbus-monitor` hook.

47
00:02:22,000 --> 00:02:25,040
That's brilliant because it ties directly
into your physical presence.

48
00:02:25,152 --> 00:02:29,680
Lock your screen, the file vanishes, and
your phone starts buzzing again to keep you

49
00:02:29,730 --> 00:02:31,200
updated while you're away.

50
00:02:31,232 --> 00:02:33,920
That is top-tier notification hygiene.

51
00:02:34,000 --> 00:02:36,960
Fair dinkum, it makes a massive difference
to your focus.

52
00:02:37,140 --> 00:02:42,960
And look, v2.1.181 didn't just stop at
notification fixes.

53
00:02:43,040 --> 00:02:47,720
They've also upgraded the engine under the
hood to Bun 1.4,

54
00:02:47,767 --> 00:02:50,480
which makes the tool start up noticeably
faster.

55
00:02:50,624 --> 00:02:55,200
Plus, they've tweaked the streaming output
so it renders line-by-line now.

56
00:02:56,000 --> 00:02:58,720
Oh, the line-by-line streaming is huge!

57
00:02:58,947 --> 00:03:02,720
It means no more of that weird, chunky
flickering in the terminal when Claude is

58
00:03:02,778 --> 00:03:03,520
responding.

59
00:03:03,680 --> 00:03:05,440
It just flows naturally.

60
00:03:05,520 --> 00:03:07,920
And they added inline config overrides,
right?

61
00:03:07,952 --> 00:03:13,360
Like, you can just type `/config
key=value` directly into the prompt to change

62
00:03:13,396 --> 00:03:16,320
settings on the fly without digging into
config files.

63
00:03:17,000 --> 00:03:20,280
Yeah, no worries about restarting your
session just to tweak a minor setting.

64
00:03:20,467 --> 00:03:23,080
It's a fantastic quality-of-life release.

65
00:03:23,384 --> 00:03:26,840
That's all we have for today's quick look
at Claude Code.

66
00:03:27,080 --> 00:03:28,440
I'm Lachlan Reed.

67
00:03:29,000 --> 00:03:29,960
And I'm James Turner.

68
00:03:30,000 --> 00:03:30,360
See ya!