codex 0.44.0 breaks input on fish
Resolved 💬 3 comments Opened Oct 4, 2025 by L3nn0x Closed Oct 5, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.44.0
Which model were you using?
_No response_
What platform is your computer?
macos m1 running 15.7, running ghostty 1.2.0 and fish 4.1.1.
What steps can reproduce the bug?
launch codex 0.44.0 from fish, the initial display shows (without the background color on the input line), however input is then broken, no key input is registered. If codex is killed (from another terminal, because ctrl+c isn't recognized either), the terminal itself doesn't recognize inputs either (it doesn't recognize signals like ctrl+d or ctrl+c either).
What is the expected behavior?
codex accepts inputs normally.
What do you see instead?
input is broken on codex launch.
Additional information
I can confirm that codex works as expected when running via zsh instead of fish.
Codex 0.42.0 was working as expected on fish. I suspect this is because of the background color on the input line.
3 Comments
Potential duplicates detected:
Powered by Codex Action
@L3nn0x I'm able to run this with the same setup (macOS 15.7, ghostty 1.2.0, fish 4.1.1) and not seeing the issue. Does it repro consistently for you?
@dylan-hurd-oai it did until I rebooted (when in doubt, reboot...), which made the issue go away. Sorry for the false report!