typing too fast doesn't send message
Open 💬 4 comments Opened Feb 23, 2026 by kalineh
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
typing fast and pressing enter sometimes does not send message, but inserts a newline
this is not a shift-enter bug
git bash, windows
quite frequent, since around 0.97~ or something (pre 1.0 definitely, but not far before that)
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Which terminal emulator are you using?
This is potentially going to be a tricky bug to repro and track down. Since you're the first one to report it, it's possible that it's specific to your configuration and system. You may need to do some diagnosis on your own. You could clone the codex repo, build it locally, and use codex to debug. If you have any insights about the root cause, please share.
I've had that bug on macOS too but only in cases when my cpu is loaded 100% so codex was slow
im using git bash in windows, but it definitely is new since around 0.96-0.99~ kinda updates
it definitely does feel like input is less responsive so it might be just performance regressions causing it, and not an enter-bug as such (that said, it indicates that input is not being handled in a buffered way properly)
the input feels similarly laggy with cmd.exe and powershell, and i can only repo it when i have like 50% context of a large session open. you can literally just type asdf fast and feel the latency tbh, just compare doing that in cmd.exe raw vs empty codex session
either way typing ping<enter> <- there should be no code path that treats that as a shift-enter, but it can