{"version":"2.1.274","anchor":"oauth-pendingstepupscope-reset-now-conditioned-on-handleredi","canonical_anchor":"oauth-pendingstepupscope-reset-now-conditioned-on-handleredi","heading":"OAuth pendingStepUpScope reset now conditioned on handleRedirection","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/oauth-pendingstepupscope-reset-now-conditioned-on-handleredi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### OAuth pendingStepUpScope reset now conditioned on handleRedirection\n\nClearing the pending OAuth step-up scope on token save now only happens when handleRedirection is set\n\n**What**\n\nWhen Claude Code saves or refreshes an MCP (Model Context Protocol) OAuth token, it can clear a stored `_pendingStepUpScope` value, which tracks a scope the user still needs to re-authorize. This clearing used to happen unconditionally on token save, or on any change to the access token, at two different call sites. Both now only clear it `if (this.handleRedirection)`.\n\n**Why**\n\nThis avoids discarding a pending re-authorization request in situations that aren't actually handling a redirect, so a scope still waiting on the user's approval isn't silently forgotten.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}