Claude Code 2.1.225

A headless job can run without a terminal window. During one, a temporary 401 error used to replace a long-lived CLAUDE_CODE_OAUTH_TOKEN with a short-lived login token, breaking the job until restart. On macOS, MCP OAuth servers could also emit a burst of 401s after a Keychain read timed out. Both cases are fixed. It was like a transit-card reader briefly failing and then cutting your monthly pass into a one-trip ticket; it no longer swaps the card.

When auto mode asks for permission and a safety filter refuses that check, the action still stays blocked. The refusal no longer counts toward the consecutive-block limit, and the model is told to move on rather than retry. Think of a self-checkout that cannot accept one coupon: staff still reject it, but do not make the machine scan the same coupon forever; it continues with the rest of the basket.

Send a message between Claude sessions from a headless environment, or during startup, and it could previously sit in a queue with neither notice nor expiry. That is fixed. A cross-session message is a handoff between separate Claude sessions; it should now produce an outcome rather than resemble a letter wedged silently inside a mailbox. You no longer need to wonder whether it is waiting forever.

With Remote Control, you can inspect or take over Claude work from another device. Resuming a huge conversation after its history was compacted could fail, while web sessions could be falsely called stuck and resend an ever-growing backlog on each reconnect. Both are fixed. It was like rejoining an online meeting where the host lost the first half of the notes and replayed every old slide; now the meeting resumes where it stopped without piling up history.

Hovering over a session from another project in the agents list could previously change the folder where the next agent started. It no longer does. Separately, if claude self-hosted-runner cannot create or write its --base-dir, it now exits with a clear startup error instead of registering and failing every session. It is like dispatch no longer sending a driver to a neighbor's address after glancing at their order, and reporting a locked garage before every trip breaks down.

Want help from a Remote Control session on another machine? SendMessage can now start a conversation with it by name; you no longer have to wait for it to write first. ListAgents shows it as name [ref]. A Remote Control recipient you already confirmed also cannot be silently replaced by a same-named local session if its remote list cannot be checked. It is registered mail: find the addressed recipient first, and do not hand the confirmed letter to a namesake.