A stale saved OAuth client for an MCP server is repaired in place instead of re-registered.
What's wrong with this entry?
When a saved OAuth client for an MCP server has an out-of-date redirect URI, Claude Code no longer always forces a fresh dynamic registration. If a client ID is configured, it updates the stored entry in place, adopting that client ID and clearing the secret, or just bringing the redirect URI into line, and uses it. Failures to write the repair are logged.
stale client_id repair
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Bundled API client: new endpoints and a stripped request field
Both mention client
-
v2.1.228
Bundled Anthropic SDK picks up beta resources
Both mention client
-
v2.1.228
API client request handling moved to a middleware chain
Both mention client