Skip to content

docs: add AgentID as a social connection - #3536

Closed
wyattjoh wants to merge 4 commits into
mainfrom
wyattjoh/agentid-social-connection
Closed

wyattjoh wants to merge 4 commits into
mainfrom
wyattjoh/agentid-social-connection

Conversation

@wyattjoh

@wyattjoh wyattjoh commented Sep 14, 2026

Copy link
Copy Markdown

🔎 Previews:

  • /docs/guides/configure/auth-strategies/social-connections/agentid
  • /docs/guides/configure/auth-strategies/social-connections/overview
  • /docs/reference/types/sso

What does this solve? What changed?

Adds a social connection guide for AgentID, to land alongside first-class agentid / oauth_agentid provider support in clerk/javascript#9735.

  • New guide at social-connections/agentid, following styleguides/SSO.STYLEGUIDE.MD.
  • Registers the page in manifest.json and in the Supported social providers card grid.
  • Adds 'agentid' to the OAuthProvider union in reference/types/sso, in the same position as the union in @clerk/shared.
  • Adds AgentID's official light and dark brand marks from https://www.agentid.com/brand.
  • 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.

Other resources

@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
clerk-docs Ready Ready Preview Sep 14, 2026 6:12pm UTC

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ 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.

@wyattjoh

Copy link
Copy Markdown
Author

This branch and PR were migrated to clerk/clerk. Migration branches/PRs created from this PR (most recent last):

@wyattjoh wyattjoh closed this Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant