Zed adds ChatGPT subscription sign-in for agent and Codex workflows

• Zed now lets users sign in to its agent with a ChatGPT subscription, and zeddotdev's launch post says those users get the same usage and rate limits they get in Codex.
• In the same rollout, zeddotdev's feature list says Zed supports four OpenAI paths: ChatGPT subscription sign-in, ACP, Codex CLI in the terminal, and direct API keys.
• WesRoth's screenshot post shows the new "Sign in to use ChatGPT Subscription" button surfaced directly inside the agent flow.
• The linked Zed blog post gives the official write-up, while OpenAIDevs' repost signals OpenAI was comfortable amplifying the third-party integration.

You can jump from the official Zed blog post to WesRoth's screenshot of the new sign-in button, and zeddotdev's thread also spells out the full OpenAI workflow menu: subscription sign-in, ACP, Codex CLI, or API key. The launch post adds the most useful operational detail, namely that subscription users keep the same Codex usage and rate limits inside Zed.

Zed's core change is simple: the agent can now authenticate with a ChatGPT subscription instead of requiring a separate API-key setup.

That matters mostly because the subscription path now sits inside the editor's own agent flow. WesRoth's screenshot shows the product surface, and testingcatalog's post framed it as ChatGPT support landing in the open-source IDE Zed.

Zed did not ship this as a one-path integration. According to zeddotdev's feature list, users can work with OpenAI models in four ways:

• sign in with a ChatGPT subscription
• connect via ACP
• run the Codex CLI in a terminal
• bring an API key

That makes the release more of a workflow unification pass than a single login button. The official write-up lives in Zed's blog post.

The strongest line in the announcement is the one about limits. zeddotdev's launch post says ChatGPT subscription users get "the same usage and rate limits" in Zed that they already get in Codex directly.

That closes the gap between editor-native and Codex-native usage more cleanly than a normal bring-your-own-key integration. zeddotdev's thread pairs that claim with the rest of the access stack, so the subscription route now sits alongside ACP, CLI, and API-key flows instead of replacing them.

Zed also used the launch to make a sharper market point. In zeddotdev's launch post, the company said it was "grateful" that OpenAI still supports subscription-based access in third-party tools "even as others move toward usage-based billing."

OpenAI did not add new detail of its own, but OpenAIDevs' repost amplified the announcement. For a low-key IDE feature, that is the clearest signal that OpenAI wants ChatGPT subscriptions to travel beyond its own first-party surfaces.