Missing 'openid' scope in dynamically registered OAuth clients

Hey @mikkokutilainen @Mohamed_Mamdouh, yeah, that’s a confusing one.

When using DCR, ChatGPT handles the OAuth client creation automatically, but it still depends on the provider correctly supporting standard OAuth/OIDC behavior, as outlined in the Developer Mode & MCP Apps guide. If a required scope isn’t included at registration time but is later requested during auth, the flow can fail.

Quick checks that would help:

• Is openid present in the DCR request and Clerk is dropping it?
• Or is it missing already in the registration payload?
• Rough timestamp with timezone of a failed attempt?

If this happens consistently with a fresh app and fresh DCR, that’s useful signal. Let’s narrow down whether this is Clerk specific or something broader.