On July 29, OpenAI began the beta rollout of Sign in with ChatGPT, which lets you use your ChatGPT account to log in to third-party services. The first wave covers six partners: Airtable, GitLab, HubSpot, Notion, Supabase and Vercel. The easiest way to picture it is as a ChatGPT version of the familiar Sign in with Google button.
ChatGPT becomes the place you log in from
Until now, ChatGPT sat on the connecting side. You added a plugin, signed in separately on the other service, and handed over permissions. This change flips that order by one step. ChatGPT itself now acts as the party that vouches for who you are, in other words an identity provider.
There are two ways to use it. The first is when you connect a supported service from the plugin directory inside ChatGPT. The second is when you press Sign in with ChatGPT or Continue with ChatGPT on the partner's own login screen. The former never takes you out of ChatGPT, while the latter simply adds one more option to the usual route in from the service side.
The feature is available globally to authenticated ChatGPT users, including people inside Enterprise organizations. If you belong to an organization, though, your admin's settings may prevent you from using it.
Only your name, email and profile picture cross over
With any mechanism like this, the first question is how much gets taken. According to OpenAI, the only things handed to the external service at sign-in are your name, your email address, and your profile picture if you have one.
Your ChatGPT conversations, memory, uploaded files, tokens and billing information are not shared just because you signed in. If a plugin asks for access beyond that, a separate approval screen appears. Passing through the door and handing over permissions inside are deliberately kept apart, and that separation is the core of the design.
There is also an escape hatch for administrators. At the organization level, you can open Access and then External Access in the global admin console and turn Sign in with ChatGPT off entirely. It is enabled by default, so organizations that have not set an explicit policy start out with it available. Restricting it to approved applications only is another option.
What actually changed at Supabase and Vercel
The partner announcements make the practical effect easier to grasp.
Supabase announced its beta support on the same day, July 29. It covers both the supabase.com login page and the Supabase plugin inside ChatGPT on desktop, web and mobile. Existing users whose email address matches their ChatGPT account do not get a second account: the two are linked automatically, and ChatGPT simply becomes one more sign-in method on the account they already have. SSO accounts are the exception and stay separate. The connection can be revoked from the dashboard at any time.
Vercel shipped support the same day. Besides showing up when you add the Vercel plugin to ChatGPT, Continue with ChatGPT now appears on the sign-in and sign-up pages for both Vercel and v0. Team requirements such as two-factor authentication and SSO still apply as before. Re-authenticating or disconnecting is handled in your account's Authentication settings.
What both companies share is a motive: shrinking the gap between where you start working in ChatGPT or Codex and where your actual backend or deployment target lives. When the place you write your first prompt and the place you create an account are different, work stops there for a moment. Seen as an attempt to erase those few dozen seconds, it is a quiet but genuinely effective kind of improvement.
Reading ChatGPT as an authentication layer
Step back and this is more than a developer convenience story. A login button is, in part, a measure of how close a service has moved to everyday infrastructure. ChatGPT joining a screen that already lists Google, Apple and GitHub also means OpenAI is taking on the role of handling people's identity information.
The six launch partners are all developer tools and workspace services, which is a natural lineup given how they pair with Codex. How far the list grows from here is an open question, but the wider it gets, the wider the blast radius if you lose access to your ChatGPT account. It is worth keeping in mind what exactly is being consolidated in exchange for the convenience.
Summary
On July 29, OpenAI released Sign in with ChatGPT in beta, allowing a ChatGPT account to serve as a login for external services. The first wave covers six services: Airtable, GitLab, HubSpot, Notion, Supabase and Vercel. Only your name, email address and profile picture are passed along, and access to conversations or files requires separate approval. Organization administrators can disable the feature outright from the console or limit it to approved applications.
