Codex agent bridge still requires API key even with MCP OAuth (can’t use ChatGPT Pro subscription)
What feature would you like to see?
Summary
I’m testing the new MCP OAuth flow with Codex Chat in bESTEEbROWSER. OAuth succeeds and we get a token back, but codex-bridge continues to reject
requests unless we provide an OpenAI API key. The release notes (e.g., rust‑v0.50.0/0.53.0) suggested OAuth improvements, so we expected that—after
authenticating through MCP—the CLI could run on a ChatGPT Pro subscription. Right now the code still errors with “Codex agent requires a valid OpenAI
API key” unless a billable API key is present.
Additional information
What happens instead
- User clicks “Connect OpenAI Account” → local MCP auth flow completes and stores access/refresh tokens.
- When POST /api/codex/agent/run is called, the backend plugin (chefskitchen-electron/backend/core/plugins/codex-bridge.plugin.js) checks for an API
key in env/Zustand state.
- Because no API key exists, the request fails with 500 and the message above.
Why this matters
ChatGPT Pro users hoped to use their subscription for Codex agent work after OAuth, without enabling pay‑as‑you‑go API billing. The current
implementation still needs an API key, so the subscription alone isn’t enough.
Requests / Questions
- Is this expected, or should MCP OAuth give us a token the SDK can exchange for an API key (or some equivalent)?
- If it’s expected, could the docs clarify that a separate API key is still required even after OAuth so ChatGPT Pro subscribers aren’t surprised?
- If an exchange endpoint is available (e.g., subject-token → API key), guidance/examples would be helpful so we can implement it in the bridge.