Sign in with ChatGPT (Beta)

v2026.9.7 lists Sign in with ChatGPT as a beta, alongside the OpenAI Agents API. This is an identity and billing path for ChatGPT/Codex subscription access. It is not a reason to expose the Gateway, and it is not the same as pasting an API key.

Linux companion docs: for OpenAI choose ChatGPT Login (subscription) or OpenAI API Key (API billing). Browser sign-in completes on the Gateway host. If that host is remote or localhost callback cannot be reached, use ChatGPT Device Pairing. See official OpenAI/OAuth notes on the Linux platform page and OpenAI setup.

Three ways to pay for OpenAI

PathUse whenWatch-outs
OpenAI API keyYou want metered Platform billing and scripts that do not depend on a browser login.Keys in env, spend caps. Platform credentials take priority over ChatGPT subscription access when both exist (September GPT Live notes).
Sign in with ChatGPT (Beta)You already pay for ChatGPT/Codex and the companion or Control UI offers ChatGPT Login.Beta. Browser callback wants to finish on the Gateway host. Remote Gateway: device pairing.
Device pairingThe Gateway is not on the same machine as the browser.Still authenticate the Gateway itself. Pairing is not a public OAuth app you put on the internet.

What does not change

  • Bind the Gateway to localhost (or a private mesh). Network isolation.
  • Android live audio on subscription auth is still documented as verification pending. Android 2026.
  • Model IDs (GPT-6 Sol, etc.) are still configured as models. Autumn models.

Related