You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds the /docs/authentication/social-connections/agentid redirect that every other provider guide has.
The AgentID-side steps were captured from the live AgentID console rather than its public docs page, which is stale — that page says "Register client", while the console says Create application and adds an Auth provider selector with a Clerk option. The Clerk-side labels match what the Dashboard renders for an AgentID connection: the value to copy is Redirect URI (not "Redirect URL", and not the "Authorization Callback URL" the Vercel guide uses), and the Scopes field is for additional scopes, so the guide only sends people there for the optional owner scopes.
Opening as a draft. The guide documents the first-class provider flow — "Select AgentID from the provider list", shared credentials for development instances — which is still gated behind a staff flag in the Clerk Dashboard. AgentID's own in-console setup guide still documents the Custom provider path, which produces oauth_custom_agentid rather than the oauth_agentid added in clerk/javascript#9735. One item left for a maintainer:
AgentID requires PKCE to bind the authorization code to the sign-in transaction; in the custom-provider flow it's a manual toggle. Whether the built-in connection enables it automatically is a backend concern, so it isn't asserted either way here.
Deadline
No rush — gated on first-class AgentID support landing in the Dashboard.
⚠️This PR cannot be merged here. The Clerk docs now live in clerk/clerk under clerk-docs/. Please migrate this PR by running:
pnpm migrate:clerk
Run it locally from the root of this branch and it'll migrate the branch and PR over to clerk/clerk and close this PR automatically. If new commits land on this PR after migration, re-running the same command is safe: it updates the existing clerk/clerk branch and PR instead of creating a new one.
The required Block merges (migration to clerk/clerk required) check on this PR will keep failing on purpose until the PR is migrated and closed.
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
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.
🔎 Previews:
/docs/guides/configure/auth-strategies/social-connections/agentid/docs/guides/configure/auth-strategies/social-connections/overview/docs/reference/types/ssoWhat does this solve? What changed?
Adds a social connection guide for AgentID, to land alongside first-class
agentid/oauth_agentidprovider support in clerk/javascript#9735.social-connections/agentid, followingstyleguides/SSO.STYLEGUIDE.MD.manifest.jsonand in the Supported social providers card grid.'agentid'to theOAuthProviderunion inreference/types/sso, in the same position as the union in@clerk/shared./docs/authentication/social-connections/agentidredirect that every other provider guide has.The AgentID-side steps were captured from the live AgentID console rather than its public docs page, which is stale — that page says "Register client", while the console says Create application and adds an Auth provider selector with a Clerk option. The Clerk-side labels match what the Dashboard renders for an AgentID connection: the value to copy is Redirect URI (not "Redirect URL", and not the "Authorization Callback URL" the Vercel guide uses), and the Scopes field is for additional scopes, so the guide only sends people there for the optional owner scopes.
Opening as a draft. The guide documents the first-class provider flow — "Select AgentID from the provider list", shared credentials for development instances — which is still gated behind a staff flag in the Clerk Dashboard. AgentID's own in-console setup guide still documents the Custom provider path, which produces
oauth_custom_agentidrather than theoauth_agentidadded in clerk/javascript#9735. One item left for a maintainer:Deadline
No rush — gated on first-class AgentID support landing in the Dashboard.
Other resources