TL;DR
SendMessage can now start conversations with Remote Control sessions on other machines (more below).
ListAgentsshows them asname [ref]; previously you could only reply after they messaged you first.Fixed a transient 401 silently replacing a long-lived
CLAUDE_CODE_OAUTH_TOKENwith a stored login's short-lived token. If headless sessions hit random auth failures until restart, update to 2.1.225.Auto mode no longer counts a safety-filter refusal of its own permission check toward the consecutive-block limit. The action is still denied, but the model is told to move on instead of retrying.
Gateway spend-limit details now surface in the usage warning. The limit-reached message names the cap, its reset time, and the operator's message (requires gateway on 2.1.225).
New in 2.1.226, 2.1.225
2.1.226 (August 8, 2026)
- Bug fixes and reliability improvements
2.1.225 (August 8, 2026)
- Added gateway spend-limit support to Claude Code's usage warning; the limit-reached message now names the cap, its reset time, and the operator's message (requires the gateway on 2.1.225)
- Added a workspace trust prompt to
claude agentsfor untrusted directories, matching the behavior ofclaude - Fixed a transient 401 replacing a long-lived
CLAUDE_CODE_OAUTH_TOKENwith a stored login's short-lived token, breaking headless sessions until restart - Fixed MCP OAuth servers on macOS intermittently failing with a burst of 401 errors, as if never authenticated, after a keychain read timed out
- Fixed auto mode counting a safety-filter refusal of its own permission check toward the consecutive-block limit; the action is still denied, but the model is now told to move on rather than retry
- Fixed cross-session messages staying parked without a notice or expiry in headless sessions and during startup
- Fixed conversation history breaking on Remote Control session resume after very large conversations were compacted
- Fixed hovering over a session in another project in the agents list changing the directory the next agent starts in
- Fixed
claude self-hosted-runnerregistering and then failing every session when--base-dircannot be created or written; it now exits at startup with a clear error - Fixed Claude Code on the web sessions being misreported as stuck, re-sending a growing event backlog on every reconnect
- Improved Remote Control: photos attached from the Claude app are now shown to Claude directly instead of being read from disk with a separate tool call
- [VSCode] Fixed Focus view folding away the latest to-do list, a pending question's context, and settled answers; thinking-only folds show "Thought for Ns" and re-collapse when their turn completes
- SendMessage can now start a conversation with your Remote Control sessions on other machines by name (
ListAgentsshows them asname [ref]), instead of only replying after they message you first - SendMessage: a Remote Control recipient you already confirmed is never swapped for a same-named session on this machine when its own list couldn't be checked
Notes
SendMessage + Remote Control: initiation, not just reply
2.1.224 added cross-session SendMessage as a discovery-and-reply system. You could list other sessions with ListAgents and message them, but Remote Control sessions on other machines only appeared after they messaged you first. 2.1.225 removes that limitation: Remote Control sessions show up in ListAgents as name [ref] and you can start the conversation. The companion fix (confirmed recipients not swapped for same-named local sessions) closes a name-collision edge case from the same arc. If you use Remote Control across machines, this is the release where SendMessage becomes a two-way channel rather than a callback.