Claude Code v2.1.225 ·
Daemon auth cooldown and status write through the v5 backend
Daemon login cooldown and status writes go through the storage backend and now surface errors instead of hiding them.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.225,
Internal ChangesSection of the release
What
The browser-login cooldown timestamp and the auth_required status file go through the storage backend when one is available instead of direct file IO.
Details
- writes use a umask-derived file mode
- backend failures raise explicit errors carrying telemetry codes rather than being swallowed
Evidence
daemon-auth v5 cooldown write failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.225 →
