Brought to you by Jellypod AI.
So I was, uh, looking through the latest update for Claude Code,
version 2.1.225, and they completely fixed one of my biggest pet peeves with remote
agent sessions.
Before this patch, if you had a remote control session running on a headless server
or a separate dev box, it had to sit there passively waiting for you to ping it
first.
Right!
It was totally reactive.
But now with version 2.1.225, SendMessage can now start a conversation with your
Remote Control sessions on other machines by name.
That is a massive shift for multi machine automation.
Yeah, mate!
You just run ListAgents to grab the, uh, the active session name,
that little name tag with the reference code, and then SendMessage can kick off a
thread across machines proactively.
You can hand off a heavy build task from your laptop to a remote dev box without
sitting around waiting to initiate it from the remote side.
Exactly.
And that pair nicely with what they did for enterprise teams on the CLI side,
too.
You know those cryptic 429 rate limit or 401 unauthorized errors you used to get
when a gateway budget cap got hit?
Oh, mate, absolute nightmare when running high volume scripts.
You had no idea if your key expired or if the company account ran out of,
uh, cash.
Well, now the CLI usage warnings pull data directly from the enterprise gateway.
So it actually outputs the exact dollar cap, the exact reset timestamp,
and any custom message your ops team left.
Like, hey, budget exceeded until midnight UTC.
No more guessing why an automated run suddenly stalled out.
No more pinging DevOps at two in the morning asking if the API is down!
That is brilliant.
And speaking of automated runs, they fixed that annoying auto mode safety loop
issue, right?
Yeah, this was a big bug fix.
Previously, if a safety filter triggered a refusal while auto mode was running,
it counted toward the consecutive block limit.
So the agent would just keep retriving blindly, hit the block threshold,
and crash out.
Ah, so it was treating a safety guardrail like a hard execution error?
Precisely.
Now, when a safety refusal happens, Claude Code explicitly instructs the model to
pivot its strategy instead of retrying the exact same blocked action.
Plus, they brought workspace trust prompts over to the claude agents command,
so if you try running background agents in an untrusted directory,
it stops and prompts you first.
That is a crucial sanity check for security.
So if someone wants to start using cross machine messaging right now,
what is the exact terminal workflow?
So, step one, run ListAgents on your controller terminal to see all registered
sessions across your devices.
Step two, copy the target session string, that name ref identifier.
Step three, invoke SendMessage passing that session name directly as the recipient.
But here is the major caveat, both machines must be updated to version 2.1.225,
or the gateway protocol will reject the cross session handshake.
Right, version parity across all your remote dev boxes or it falls flat.
And make sure your headless sessions are set up to clear parked notifications
properly so you do not pile up unread messages in the background.
Good stuff.
Catch you all next time!