Sign in with ChatGPT brings plan usage to other apps
Sign in with ChatGPT lets eligible subscribers use their allowance in partner apps. Here is how permissions, usage caps and optional credits work.
OpenAI is extending the reach of a ChatGPT subscription into other companies’ software. Sign in with ChatGPT was part of its September 29 DevDay announcements, with separate options for account access and eligible AI usage.
The useful question is what each connection actually grants. A familiar login button can now sit beside a decision about which application gets to spend part of an existing AI allowance. Those choices deserve separate attention before connecting a service.
One account with two different permissions
OpenAI’s identity documentation says the login option is available globally to authenticated ChatGPT users, subject to organization policies and support from the application. Basic identity sharing supplies a name, email address and profile picture when one exists.
That login does not independently expose conversations, saved memory, files or billing information. An application can ask for additional access through a separate authorization process. Users can complete the identity step without approving subscription sharing.
For organizations, existing application allow and deny policies remain in effect. Global administrators manage the relevant organization permissions. A workspace administrator does not automatically have authority over those broader settings.
Which partners support plan usage
The official partner directory separates applications that can use a ChatGPT plan from applications that offer login alone. It lists Devin, Notion, Vercel, Warp and several other tools under plan usage. Airtable, Canva, GitLab, HubSpot and Supabase appear in the login only group. Lovable is marked as coming soon.
Open source integrations have their own section, including OpenClaw, OpenCode, Pi and T3. Readers should check the current directory and the application’s own connection screen rather than assume that every ChatGPT login includes the same functionality.
The allowance stays shared
According to the plan usage guide, Plus and Pro subscribers can authorize eligible requests against their included Work and Codex allowance. An application may still charge for its own subscription or services.
| Control | What it does |
|---|---|
| Weekly app limit | Caps an app’s share of overall weekly usage |
| Credit permission | Allows available credits after included usage ends when eligible |
| Disconnect | Ends the app’s authorized connection to ChatGPT |
An app cap creates neither extra allowance nor a reserved allocation. Credit use is off by default. Where supported, it requires a separate opt in and an app limit of 100 percent. Automatic credit purchases are another setting, and continued usage can trigger charges when those purchases are enabled.
Signing out of an app does not disconnect its ChatGPT authorization. Disconnecting also does not undo recorded usage or delete information the app already received.
Developers have a narrower integration surface
The developer overview covers open source and locally hosted applications. Developers of paid or remotely hosted products are directed to an interest form.
The preview limitations are substantial. This route requires streaming Responses API requests without server storage. It excludes hosted image generation, file search, Code Interpreter and native computer use. Audio and video inputs are also unsupported through this flow. Developers should check their required tools before promising compatibility.
Our report on GPT 6.1 Sol pricing covers a different purchasing decision, direct API usage. Here, the central tradeoff is allocation. Someone who moves demanding jobs into a partner app should watch the allowance left for their other work, as well as any separate bill from that partner.
