Codex CLI v0.63.0 always interrupts conversation and hangs on basic prompts (Pop!_OS)

Resolved 💬 4 comments Opened Nov 29, 2025 by ghost Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex --version OpenAI Codex (v0.63.0)

What subscription do you have?

ChatGPT Plus + Project API Key (with active billing credits)

Which model were you using?

gpt-5.1-codex-max (reasoning: medium)

What platform is your computer?

Pop!_OS 22.04 (Ubuntu-based) Linux x86_64 (node v20.19.6, npm v11.6.4)

What issue are you seeing?

Title: Codex CLI v0.63.0 interrupts every prompt and produces no output

Version:
OpenAI Codex (v0.63.0)

Subscription:
ChatGPT Plus + Project API Key

Model:
gpt-5.1-codex-max

Platform:
Pop!_OS 22.04 (Ubuntu)
Linux x86_64
node v20.19.6
npm v11.6.4

Issue Description:
Codex CLI authenticates successfully but cannot respond to any prompt. Every message immediately fails with:

■ Conversation interrupted - tell the model what to do differently. Something went wrong?

This happens with simple inputs like "hello". Codex never produces output. /status shows a valid session, valid API key, and zero tokens used. Other OpenAI APIs work fine on this machine.

Example:
$ codex

hello

■ Conversation interrupted - tell the model what to do differently. Something went wrong?

$ codex /status
Model: gpt-5.1-codex-max
API key configured
Session: 019acd8f-2841-7a50-a804-99571fb9ea4a
Token usage: 0 total

Steps to Reproduce:

  1. Install Codex with: npm i -g @openai/codex
  2. Run: codex
  3. Authenticate with ChatGPT login or project API key
  4. Type any prompt (e.g., "hello")
  5. Codex immediately fails with the above error

Expected Behavior:
Codex should respond with completions or perform actions. Instead, every prompt is interrupted and no output is generated.

Additional Info:

  • Issue occurs 100% of the time
  • Reinstalling does not fix it
  • Using ChatGPT login or project key makes no difference
  • All other OpenAI API calls work normally

What steps can reproduce the bug?

  1. Install Codex CLI:

npm i -g @openai/codex

  1. Launch Codex:

codex

  1. Authenticate using either:
  • ChatGPT Plus login, or
  • Project API key
  1. After Codex loads, type any prompt:

hello

  1. Codex immediately fails with:

■ Conversation interrupted - tell the model what to do differently. Something went wrong?

This happens 100% of the time, even in an empty directory and even with different authentication methods.

Session ID example:
019acd8f-2841-7a50-a804-99571fb9ea4a

Token usage:
0 total (0 input / 0 output)

Context window usage:
0 used / 272K available

Codex does not execute any tasks and does not generate any output.

What is the expected behavior?

Codex CLI should accept a prompt and generate a normal model response. For simple inputs like "hello," Codex should return a short completion instead of interrupting the conversation. For coding-related tasks, Codex should analyze the directory, read files, propose edits, or execute agent actions without failing immediately.

In general, expected behavior is:

  • Codex processes the input prompt
  • Codex produces a model-generated response or action plan
  • Token usage increases from 0
  • The session continues normally without interruption

Instead, Codex stops instantly with an error and provides no output.

Additional information

Codex CLI worked previously on this same machine but began failing recently without any configuration changes. The issue persists across reinstalls, different directories, different authentication methods, DNS resets, and system restarts. Other OpenAI API tools (curl requests and the official OpenAI CLI) work correctly with the same project API key. This failure appears isolated to the Codex CLI executable itself.

If helpful: DNS resolution for cli.openai.com returns NXDOMAIN on all major resolvers (Cloudflare, Google), while other OpenAI domains resolve correctly. This may indicate an upstream infrastructure issue affecting the CLI.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #7184

Powered by Codex Action

ghost · 9 months ago

Title: Codex CLI rejects valid project API keys — "invalid_api_key" &
Conversation interrupted

Description:
Hi — I’m hitting an auth failure when trying to run the Codex CLI with a
project API key. I’ve followed the documented steps: removed
~/.codex/auth.json, set ~/.codex/config.toml with preferred_auth_method
= "apikey"
, exported OPENAI_API_KEY in the shell, and use codex-cli
v0.63.0
. /status shows “API key configured (run codex login to use
ChatGPT)”, but any attempt to talk to the model returns “Conversation
interrupted” and curl requests to the API return:

{"error":{"message":"Incorrect API key provided:
sk-proj-****CTED","code":"invalid_api_key"}}

What I tried:

  • Created >30 fresh Project API keys (sk-proj-...), exported them in the

shell, and tested with curl — every key returns invalid_api_key.

  • Confirmed environment variable is set in the same terminal from which I

launch Codex.

  • Deleted ~/.codex/auth.json and ~/.codex/sessions.
  • Updated Codex CLI to latest (v0.63.0).

Diagnostics (redact keys before posting):

  • codex --version: v0.63.0
  • /status block: [paste full /status output here]
  • ~/.codex/config.toml: [paste contents]
  • tail -n 200 ~/.codex/log: [paste the last ~200 lines]
  • curl output (redact the key): [paste curl response which contains

invalid_api_key]

Problem summary:
Codex CLI appears to be sending a key that the backend rejects with
invalid_api_key. The same keys created in the platform UI consistently
return the invalid API key error when used from my machine. This prevents
Codex from establishing a conversation (Conversation interrupted /
Reconnecting). My account: @.***

Please advise whether:

  1. There’s an org/project restriction preventing project keys from working

with Codex CLI, or

  1. There’s a bug in the CLI’s API-key authentication path that mangles keys

or uses the wrong header, or

  1. Something in the backend is rejecting project keys generated for my

account.

I can provide additional logs or live debugging info on request. Thanks.

On Fri, Nov 28, 2025 at 9:13 PM github-actions[bot] <
@.***> wrote:

github-actions[bot] left a comment (openai/codex#7377) <https://github.com/openai/codex/issues/7377#issuecomment-3590941275> Potential duplicates detected. Please review them and close your issue if it is a duplicate. - #7184 <https://github.com/openai/codex/issues/7184> Powered by Codex Action <https://github.com/openai/codex-action> — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/7377#issuecomment-3590941275>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPLRH3JX7OY6KMBXQNRGUUT37EFNBAVCNFSM6AAAAACNQSSQY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJQHE2DCMRXGU> . You are receiving this because you authored the thread.Message ID: @.***>
etraut-openai contributor · 5 months ago

This bug report hasn't received any upvotes or additional posts in three months. Closing.

gatewaytofredom · 1 month ago

Im experiencing this as well now on Ubuntu with codex-cli 0.142.0