Unclear Which requests skip the token refresh after a 401 is not known.
What
A 401 is the error a server returns when it rejects your sign-in. Claude Code usually reacts by refreshing your sign-in token, the credential that proves who you are. That handling now has an option to stop before the refresh is tried.
When a host program manages your sessions, cloud-sessions calls now keep the sign-in token, and a 401 there is taken as that token's own. Before, the host's answer for the sign-in token was cleared.
Why
This changes how sign-in errors are recovered when sessions are managed by a host program.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which requests skip the token refresh after a 401 is not known.