1
00:00:00,079 --> 00:00:01,819
Brought to you by Jellypod AI.

2
00:00:03,259 --> 00:00:06,399
So I was, uh, looking through the latest
update for Claude Code,

3
00:00:07,059 --> 00:00:13,359
version 2.1.225, and they completely fixed
one of my biggest pet peeves with remote

4
00:00:13,439 --> 00:00:14,219
agent sessions.

5
00:00:14,960 --> 00:00:19,139
Before this patch, if you had a remote
control session running on a headless server

6
00:00:19,199 --> 00:00:24,180
or a separate dev box, it had to sit there
passively waiting for you to ping it

7
00:00:24,260 --> 00:00:24,659
first.

8
00:00:24,907 --> 00:00:25,167
Right!

9
00:00:25,268 --> 00:00:26,727
It was totally reactive.

10
00:00:27,208 --> 00:00:33,528
But now with version 2.1.225, SendMessage
can now start a conversation with your

11
00:00:33,567 --> 00:00:37,387
Remote Control sessions on other machines
by name.

12
00:00:37,887 --> 00:00:40,728
That is a massive shift for multi machine
automation.

13
00:00:41,171 --> 00:00:41,831
Yeah, mate!

14
00:00:42,451 --> 00:00:45,851
You just run ListAgents to grab the, uh,
the active session name,

15
00:00:46,411 --> 00:00:50,891
that little name tag with the reference
code, and then SendMessage can kick off a

16
00:00:50,931 --> 00:00:53,252
thread across machines proactively.

17
00:00:53,311 --> 00:00:57,552
You can hand off a heavy build task from
your laptop to a remote dev box without

18
00:00:57,591 --> 00:01:00,011
sitting around waiting to initiate it from
the remote side.

19
00:01:00,322 --> 00:01:00,922
Exactly.

20
00:01:01,323 --> 00:01:04,602
And that pair nicely with what they did
for enterprise teams on the CLI side,

21
00:01:04,642 --> 00:01:04,842
too.

22
00:01:05,602 --> 00:01:10,822
You know those cryptic 429 rate limit or
401 unauthorized errors you used to get

23
00:01:10,862 --> 00:01:12,362
when a gateway budget cap got hit?

24
00:01:12,536 --> 00:01:16,616
Oh, mate, absolute nightmare when running
high volume scripts.

25
00:01:17,176 --> 00:01:21,177
You had no idea if your key expired or if
the company account ran out of,

26
00:01:21,257 --> 00:01:22,177
uh, cash.

27
00:01:22,557 --> 00:01:26,956
Well, now the CLI usage warnings pull data
directly from the enterprise gateway.

28
00:01:27,016 --> 00:01:30,856
So it actually outputs the exact dollar
cap, the exact reset timestamp,

29
00:01:31,236 --> 00:01:33,536
and any custom message your ops team left.

30
00:01:33,616 --> 00:01:36,056
Like, hey, budget exceeded until midnight
UTC.

31
00:01:36,536 --> 00:01:39,097
No more guessing why an automated run
suddenly stalled out.

32
00:01:39,944 --> 00:01:43,684
No more pinging DevOps at two in the
morning asking if the API is down!

33
00:01:44,364 --> 00:01:45,184
That is brilliant.

34
00:01:45,844 --> 00:01:50,545
And speaking of automated runs, they fixed
that annoying auto mode safety loop

35
00:01:50,604 --> 00:01:51,164
issue, right?

36
00:01:51,375 --> 00:01:53,415
Yeah, this was a big bug fix.

37
00:01:53,448 --> 00:01:57,375
Previously, if a safety filter triggered a
refusal while auto mode was running,

38
00:01:57,428 --> 00:01:59,615
it counted toward the consecutive block
limit.

39
00:01:59,748 --> 00:02:03,535
So the agent would just keep retriving
blindly, hit the block threshold,

40
00:02:03,555 --> 00:02:04,335
and crash out.

41
00:02:04,473 --> 00:02:08,492
Ah, so it was treating a safety guardrail
like a hard execution error?

42
00:02:08,583 --> 00:02:09,223
Precisely.

43
00:02:09,363 --> 00:02:14,423
Now, when a safety refusal happens, Claude
Code explicitly instructs the model to

44
00:02:14,490 --> 00:02:19,063
pivot its strategy instead of retrying the
exact same blocked action.

45
00:02:19,191 --> 00:02:23,463
Plus, they brought workspace trust prompts
over to the claude agents command,

46
00:02:23,543 --> 00:02:26,903
so if you try running background agents in
an untrusted directory,

47
00:02:26,983 --> 00:02:28,663
it stops and prompts you first.

48
00:02:28,766 --> 00:02:31,246
That is a crucial sanity check for
security.

49
00:02:31,706 --> 00:02:35,226
So if someone wants to start using cross
machine messaging right now,

50
00:02:35,286 --> 00:02:37,186
what is the exact terminal workflow?

51
00:02:37,208 --> 00:02:42,248
So, step one, run ListAgents on your
controller terminal to see all registered

52
00:02:42,301 --> 00:02:44,008
sessions across your devices.

53
00:02:44,168 --> 00:02:49,128
Step two, copy the target session string,
that name ref identifier.

54
00:02:49,288 --> 00:02:54,328
Step three, invoke SendMessage passing
that session name directly as the recipient.

55
00:02:54,468 --> 00:03:00,968
But here is the major caveat, both
machines must be updated to version 2.1.225,

56
00:03:01,101 --> 00:03:04,728
or the gateway protocol will reject the
cross session handshake.

57
00:03:04,848 --> 00:03:08,667
Right, version parity across all your
remote dev boxes or it falls flat.

58
00:03:09,487 --> 00:03:12,688
And make sure your headless sessions are
set up to clear parked notifications

59
00:03:12,727 --> 00:03:16,307
properly so you do not pile up unread
messages in the background.

60
00:03:17,128 --> 00:03:17,647
Good stuff.

61
00:03:18,307 --> 00:03:19,227
Catch you all next time!