Claude Code 2.1.225: OAuth token and MCP auth fixes, gateway spend limits
Mostly reliability work around authentication and Remote Control. The notable fix: a transient 401 could replace a long-lived CLAUDE_CODE_OAUTH_TOKEN with a stored login's short-lived token, breaking headless sessions until restart.
PUBLISHED2026-08-07
OBSERVED2026-08-11
AGE4d
SOURCES1
- 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 after a keychain read timed out
- Added gateway spend-limit support to the usage warning; the limit-reached message 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 SendMessagecan 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- Fixed auto mode counting a safety-filter refusal of its own permission check toward the consecutive-block limit
- Fixed cross-session messages staying parked without notice or expiry in headless sessions and during startup
- Fixed
claude self-hosted-runnerregistering and then failing every session when--base-dircan't be created or written; it now exits at startup with a clear error - Fixed conversation history breaking on Remote Control session resume after very large conversations were compacted
- Fixed web sessions being misreported as stuck and re-sending a growing event backlog on every reconnect
COMMUNITY
No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.