Codex Is Live in Zed (zed.dev)

Zed now supports OpenAI’s Codex out of the box via the Agent Communication Protocol (ACP): you can pick Codex from the New Thread menu the same way you would Claude Code or Gemini CLI. This integration is UI-only — billing and legal terms remain directly between you and OpenAI, Zed does not charge for external agents, and prompts/code sent through the Codex-ACP path do not touch Zed’s servers. Zed also open-sourced the codex-acp adapter so teams can reuse it outside the editor. The move follows broader ACP adoption across editors (Neovim, Emacs) and IDEs (JetBrains), signaling ACP’s growing role as a standard for connecting LLM-based agents to developer tools. Technically, the integration highlights important agent differences that affect workflow: some agents allow model switching mid-conversation or persist conversation state, others do not. A notable implementation detail with Codex is that its agent runs terminal commands in its own process and streams raw output bytes back to the client, rather than asking the client to execute commands. That affects terminal behavior: Zed can use PTY mode for interactive, colorful terminals but risks agent deadlocks (e.g., git rebase opening an editor); non-PTY mode reduces interactivity and colors but is more robust for automation. Having agents that support both modes lets Zed compare experiences and refine ACP guidance as the community drives future integrations.