Claude Code 2.1.225: headless token fix, Auto refusals stop counting
The point release ends a 401 bug that broke headless CI and cron runs, keeps safety refusals off your Auto block limit, and spells out gateway spend caps.
Copy markdown
The headless-session 401 bug is fixed
A transient 401 was swapping your long-lived OAuth token for a short-lived login token, silently breaking headless runs — CI jobs, cron, pipelines. 2.1.225 stops it, so update before your next automated Claude Code run.
Auto mode stops burning your block budget on refusals
Safety-filter refusals no longer count toward the consecutive-block limit that halts an Auto session. The fix lands right before Auto becomes the default for Pro, Max, and Team on Aug 14.
Gateway spend limits now name the number
When a gateway cap is hit, the limit-reached message now shows the cap amount, its reset time, and the operator's note — so Team and Enterprise users see exactly why they're throttled and when it clears.
Cross-session handoffs get less flaky
Headless cross-session messages no longer sit parked with no notice or expiry, and SendMessage can now start a Remote Control conversation by session name without swapping recipients — cleanup on the session-to-session messaging that shipped this week.
`claude agents` now asks before trusting a folder
Running agents in an untrusted directory triggers the same workspace-trust prompt as plain `claude`. A macOS fix also clears MCP OAuth servers that were hanging on keychain-read timeouts.