Replies: 1 comment
-
For me Codex seems unusable. I have happily used Claude Code, Goose, Plandex, Warp Terminal, and Aider. Every one of them has a good interface that is easily understood and generally does what you expect it to with keymaps. Codex is barely functional for me. The amount of times it has just gone haywire, the screen looking crazy, command output not showing up, keys not doing anything you expect them to, ugh. There are so many good examples of command line interfaces, be it an REPL or a full TUI like oterm. I have no idea why this team used the tools or frameworks they did. Within 30 minutes of installing and attemptingt to use Codex it had gotten "429" errors and exited (losing all context), twice. The command.stdout that showed up on my screen, one out of three showed no output, just sat there. Resizing the window or moving it to another monitor moved the input box half way up the window and drew all of the lines in a mess where I had no idea where the cursor was on my screen. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Maybe I'm the only one as I don't see a prior Discussion, Issue or Pull Request generated. 🤷♂️
I'm on a Mac with zsh and the Codex REPL seems non-standard making it abnormally difficult to use.
This is just what I've noticed in the short time using it:
Note: the standard
node
REPL is exactly what I want so I don't know why Codex is doing things differently.Codex found this in the Codex code:
At this point, unless I immediately go to the vi editor (via Ctrl+E) where keybinding and navigation are consistent, I cannot use Codex.
Beta Was this translation helpful? Give feedback.
All reactions