Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 543f575. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Add a default-off native OAuth consumer without changing MCP hosting, public discovery or existing Clerk/API-key authentication.
Deployment order
Depends on kernel/kernel#4236 being deployed first. Keep
OAUTH_NATIVE_ENABLED=falseuntil the issuer and test intermediary are configured. No deployment, DNS/discovery change or activation is included. Existing/mcphosting remains unchanged.Configuration uses only server-pinned issuer URLs, audiences, public keys, recovery epoch and an explicit intermediary client credential. JWT headers/claims never supply a fetch destination. Native connection context is not cached; independent API authorization still applies on every tool call. The issuer currently closes unsupported delegation/credential-producing API surfaces, so this is not full native tool parity.
Validation
bunx tsc --noEmitpassed.