CLI version on arch is not responding to any commands
Resolved 💬 11 comments Opened Mar 16, 2026 by akshansh-thakur Closed May 14, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.114.0
What subscription do you have?
Go
Which model were you using?
gpt-5.4 medium
What platform is your computer?
Linux 6.19.6-zen1-1-zen x86_64 unknown
What terminal emulator and version are you using (if applicable)?
Arch-linux's Console (CLI)
What issue are you seeing?
I opened codex today and when i typed my command it just returned another line. There was no output of any command I typed, then when I typed /exit it did not exit codex and just returned a new line.
What steps can reproduce the bug?
<img width="1778" height="648" alt="Image" src="https://github.com/user-attachments/assets/ba9a6341-cb9b-489c-acf0-368f219aba38" />
This is the snippet and i have tried uninstalling npm and logout and login and checked my API. Everything is working from my end.
What is the expected behavior?
_No response_
Additional information
_No response_
11 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Do you have reason to think this is a recent regression? Does it work if you downgrade to 0.113.0 or an earlier version?
Having this issue as well, just stopped responding. Completely different machine. MacOS darwin, latest version. Killing all processes did not fix the issue.
Please use
/feedbackto upload logs and post thread ID here.@etraut-openai
019cf7e2-1fdf-7a30-a3a8-b6ee98c2d9dcthread IDNow happening on multiple computers with different accounts. Is there an outage?
@etraut-openai tried downgrading codex and changing models too, but it didn't worked and then also tried by uninstalling latest codex -> downgrading npm -> installing through downgraded npm -> still no progress.
It's working for me now... out of nowhere. Not sure what this is about.
@divmgl any idea what you did?
Are you still able to repro this problem with the latest version (0.118.0)?
Closing because of lack of response.