OAuth flows no longer retry after an explicit denial

What

When you explicitly deny an OAuth authorization prompt, Claude Code now recognizes this as a deliberate choice rather than a failure. Previously, an explicit denial was handled the same way as a timeout or generic OAuth error, which triggered a retry/reset path (clearing stored client IDs and holding pending flow state). Now, error text matching OAuth error: access_denied is detected and excluded from that retry path.

• This applies to the MCP OAuth flow.
• This applies to the OAuth device-authorization flow.

Why

This avoids unnecessary retries or state resets when you've intentionally said no to an OAuth connection, rather than treating your denial like a transient network or timeout failure.