Short version: OpenAI has started rolling out "Sign in with ChatGPT" in beta — a federated login button, ChatGPT as the identity provider, the same shape as Sign in with Google or Apple. The first partners are Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel. A partner receives only your name, email, and profile picture; anything more a plugin wants is a separate consent screen you approve on its own. The convenience is the small story. The real one is direction: your signup can now start inside ChatGPT and Codex, in front of the builders already there. If those are your users, add it — behind your existing auth. If they're not, it's a beta dependency you can wait on.
What actually shipped#
A login button. When a user clicks Sign in with ChatGPT on a partner product, they authenticate with their ChatGPT account and can create or link an account in a few steps, then keep working with that service inside ChatGPT or Codex. Two of the launch partners — Supabase and Vercel — have already posted their own guides to turning it on, alongside Airtable, GitLab, HubSpot, and Notion. OpenAI's own release notes frame it as the start of an ecosystem, and Greg Brockman said as much: "supporting an ecosystem with Sign in with ChatGPT."
What a partner gets at login is deliberately thin: your name, email address, and profile picture when available. It is not a permissions grab. If a plugin or connector then wants to do something on your behalf, that access is a separate review-and-approve step the user sees on its own — so authentication (who you are) and authorization (what an agent may do) stay two distinct screens.
Why this is bigger than one less password#
The convenience framing undersells it. A login button is a funnel play, and it runs in two directions:
- Inbound to your product. A user signs in to your app with their ChatGPT account — one fewer password, faster signup.
- Outbound onto OpenAI's surface. A user inside ChatGPT or Codex adds your plugin/connector and links an account in the same motion — your product gets discovered and onboarded from inside the place a growing share of builders already work.
Direction 2 is the one that matters. It makes ChatGPT a place where accounts on your product are born. That's exactly why Google and Apple wanted to be login buttons: whoever owns the identity owns the top of the funnel, and every partner who integrates makes the broker more central. The agent era is just where that old land-grab now points — a dynamic we walked through in The OAuth Wall.
Should you add it?#
Decide by where your users already are — not by the novelty.
- Your buyers are ChatGPT-native builders (dev tools, APIs, agent products). Add it now, wired behind your existing auth as one more federated option. The prize isn't SSO; it's the distribution foothold inside ChatGPT and Codex. Instrument how many signups actually originate there so you can weight it honestly.
- Mixed prosumer/SaaS audience. Add it as one button beside Google/Apple/GitHub — never the only path. The profile data is thin and the surface is beta; the cost is one more provider to maintain.
- Regulated, enterprise, or identity-sensitive. Wait for GA and a proper data-processing and security review. Keep your own identity provider authoritative; a beta external broker in your trust chain is not where to move first.
One rule cuts across all three: keep the identity step and the capability grant separate. "Sign in with ChatGPT" authenticates a human. Granting an agent a scoped, revocable token to act on a resource is a different flow — an MCP authorization or an OAuth delegation — and it's the one that carries real blast radius. We covered the authorization side in MCP's OAuth authorization and OAuth token exchange for agent delegation. If owning your identity layer outright matters more than the funnel, Better Auth is the counter-position.
The one move this week#
If ChatGPT-native builders are your users, add Sign in with ChatGPT as a federated option today and measure the origin of the signups it brings — the button is the cheap part; the distribution is the point. If they're not, note it, keep your auth authoritative, and wait for GA. Either way, don't rebuild your login around a beta identity provider — add a provider, don't adopt a dependency.
This is one thread in a busy week; the full board — the EU's transparency clock, the model price war, and the frontier models breaking out of their own test sandboxes — is in this week's Founder's Wire.
