Question: Using Codex CLI with Continue.dev via ChatGPT login

[UW-Yury]

Hi everyone,

I have the following setup:

• VS Code
• ChatGPT Team subscription
• Docker

I’d like to know if it’s possible to use Codex CLI inside Continue.dev by logging in via ChatGPT (instead of using OpenAI API tokens).

• Could this perhaps be achieved through the MCP Servers functionality in Continue?
• Or maybe by leveraging the Docker MCP Toolkit?

Any guidance or examples on how to connect Continue with Codex CLI would be greatly appreciated.

Thanks!

[bdougie]

Out of curiosity what the goal here?

[UW-Yury]

Goal: since Codex CLI can run via ChatGPT login (no OpenAI API tokens), I’m exploring whether I can run Codex CLI as an MCP server and have Continue send tool calls to it. I’m trying to unify a few AI tools into one workflow (VS Code + Continue + Docker), so I’m experimenting with different integration paths.

Why this approach

• Avoid managing API keys—reuse my ChatGPT Team login.
• Reuse Codex CLI’s behaviors/commands from within Continue’s chat/agents.
• Keep everything containerized when possible (Docker), so it’s reproducible.

What I’m testing

• If Codex CLI exposes (or could expose) an MCP-compatible server, Continue could call it directly as a tool provider.
• If not, I could add a thin MCP shim that shells out to Codex CLI commands, runs them in Docker, and returns structured results to Continue.

What would help

• If there’s a cleaner/official pattern for using external CLIs with Continue (especially anything MCP-related), I’d love to hear examples.
• If there’s a more elegant way to use Codex CLI from the Continue extension (without rolling my own shim), I’d really appreciate any guidance or a nudge in the right direction.

Thanks!

[UW-Yury]

I’ve figured it out myself 🙂

• I used the project mcp-proxy
• Built a new Docker image with all the required packages, installed mcp-proxy, and launched Codex CLI in MCP server mode. The container runs Codex internally, while mcp-proxy exposes a streaming HTTP endpoint outside.
• This setup allowed me to connect Codex to Continue successfully