The GenAI Field Guide · Trending

Sign in with ChatGPT

An OpenID Connect sign-in that can also let a ChatGPT subscriber spend their plan's included usage inside a third-party app instead of an API key.

Sign in with ChatGPT started in July 2026 as an identity button and became, at DevDay on 29 September 2026, a way for Plus and Pro subscribers to point the usage already included in their plan at partner apps such as Devin, Amp, Warp, Kilo Code, Notion and Vercel. Under the name it is two separate OAuth grants: identity, and a scoped right to call the Responses API against the user's plan. Anyone building a developer tool or AI feature should understand it, because it moves who pays for inference from the app to the user's existing subscription.

What it is

There are two capabilities behind one button, and OpenAI's developer docs keep them apart. The first is ordinary federated login: an app adds Continue with ChatGPT, the user authenticates at OpenAI, and the app receives a verified identity with name, email and profile picture. OpenAI's docs state that identity scopes do not grant access to ChatGPT conversations or OpenAI API resources. The second is plan usage, which coverage calls token sharing: with a separate consent, the app can send model requests that are billed against the user's ChatGPT plan rather than a developer API key or the app's own credits.

The identity half launched in beta in July 2026 with partners such as Airtable, GitLab, HubSpot, Notion, Supabase and Vercel, as reported by Trending Topics. The DevDay announcement added plan usage, with 16 launch partners. Press lists differ, but the names that recur are Cognition's Devin, Amp, Warp, Kilo Code, OpenCode, OpenClaw, T3, Conductor, Dactyl, Notion and Vercel, with Lovable described as coming soon. One report separates sign-in-only partners (Airtable, Canva, GitLab, HubSpot, Supabase) from those that also accept plan usage.

Under the marketing, this is OpenAI turning a consumer subscription into a portable inference budget. Unofficial tools had already been reusing Codex logins to reach subscription usage; The New Stack describes the new feature as the officially supported replacement, with per-app tracking and limits managed in ChatGPT settings. For app makers it removes the API key setup step and the cost of serving the user's model calls. For users it means one subscription can fund several tools, within one shared weekly allowance.

How it works

Sign-in is OAuth 2.0 Authorization Code with PKCE plus OpenID Connect, against an issuer at auth.openai.com with a published discovery document and JWKS. A web app gets a client ID beginning oaiapp_, registers exact callback URLs, verifies the ID token signature, issuer, audience, expiry and nonce, keys the account on the sub claim rather than the email, and then issues its own first-party session cookie. The docs allow public clients with no secret and confidential clients using HTTP Basic client authentication.

Plan usage adds scopes on top of identity. For open-source and locally run apps the docs describe dynamic registration: the first sign-in uses a placeholder client ID with an app name hint, the user approves in the browser, and OpenAI issues a permanent oaiapp_ client ID for that install. The flow uses a loopback callback on 127.0.0.1, requests openid profile email offline_access resource.invoke chatgpt.tokens.use.direct, and names the OpenAI API as the token's resource. The app must check that chatgpt.tokens.use.direct was actually granted before offering plan usage, and store credentials with owner-only file permissions.

With that access token the app calls the public Responses API. Kilo's docs note that Chat Completions is not supported this way and that not every OpenAI model qualifies. Usage draws on the same weekly allowance as ChatGPT Work and Codex. In ChatGPT settings the user sees each connected app and can set a per-app cap, which Kilo's docs say defaults to 100 percent of the allowance. Most coverage says requests simply stop with an error at the cap; BigGo reports that credits beyond the plan can be spent only if the user has opted in and left the app at 100 percent, with that option off by default.

Disconnecting is separate from signing out. BigGo reports that signing out of a partner app does not remove its connection; you remove it in ChatGPT settings, and removing it neither restores used allowance nor deletes data the app already holds, which you must request from the app itself.

How to use it

As a user you need a ChatGPT Plus or Pro plan and a partner app that supports plan usage. As a builder, open-source and locally run apps can use plan usage now through dynamic registration, while commercial apps join a limited trial through their OpenAI representative, per OpenAI's developer docs as read on 2 October 2026.

  1. As a user, pick a launch partner you already use, such as Kilo Code, and choose Sign in with ChatGPT; in Kilo this sits on its bring-your-own-key page under OpenAI (ChatGPT subscription).
  2. Read the consent screen on OpenAI's site. Identity and plan usage are separate grants, so confirm which one the app is asking for before approving.
  3. Open ChatGPT settings, find the connected app's usage limit and lower it from the default so one tool cannot drain the weekly allowance your other work depends on.
  4. As a builder, read OpenAI's Sign in with ChatGPT quickstart and decide whether you need identity only (openid profile email) or plan usage as well.
  5. For an open-source or local app, follow the cookbook's dynamic registration flow: PKCE, a 127.0.0.1 loopback callback, save the issued oaiapp_ client ID, and request the resource.invoke and chatgpt.tokens.use.direct scopes.
  6. Verify the ID token against OpenAI's JWKS, check the granted scopes, then send a test request to the Responses API with the user's access token before building features on it.
  7. Handle the cap as a normal error path: show the user that their ChatGPT allowance or app limit is spent, and offer an API key or your own billing as an explicit alternative rather than a silent fallback.

Use cases

Sources

  1. Sign in with ChatGPT quickstart, OpenAI Developers, 2026-10-02
  2. Sign in with ChatGPT on your website, OpenAI Developers, 2026-10-02
  3. Registration and sign-in for open-source apps, OpenAI Developers, 2026-10-02
  4. Integrating Sign in with ChatGPT in your open-source app, OpenAI Cookbook, 2026-10-02
  5. Anaconda's Kilo partners with OpenAI to bring Sign in with ChatGPT to AI builders, Anaconda, 2026-09-29
  6. Using ChatGPT subscriptions with Kilo Code, Kilo, 2026-10-02
  7. OpenAI makes Sign in with ChatGPT a way to use your subscription in third-party developer tools, The New Stack (via daily.dev summary), 2026-09-29
  8. OpenAI launches Login with ChatGPT and routes plan usage into third-party AI apps, RuntimeWire, 2026-09-29
  9. Sign In With ChatGPT: Take your AI tokens to other apps, Trending Topics, 2026-09-30
  10. OpenAI launches Sign in with ChatGPT feature, letting apps draw on subscriber plans, BigGo Finance, 2026-09-30
  11. You can now spend your ChatGPT plan's usage inside other apps, Tech City Authority, 2026-09-30
  12. OpenAI DevDay 2026, BenchLM, 2026-09