Codex Truncates Chat Messages When Scrolling
Resolved 💬 25 comments Opened Nov 9, 2025 by PaulSolt Closed Apr 5, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
Scrolling up or down in Codex can cause chat messages to be partially overwritten or clipped, resulting in missing content. This makes it impossible to review previous messages accurately, especially during longer conversations.
<img width="649" height="318" alt="Image" src="https://github.com/user-attachments/assets/8b603273-5089-4cb8-9d4b-dcd179aeb959" />
---
Steps to Reproduce
- Ask codex questions
- Go back and forth, optionally adding messages to the queue.
- Attempt to scroll up and down in the chat history after the message has loaded.
- Observe whether message content changes, disappears, or becomes truncated.
(Note: The issue is intermittent and may not occur on every scroll.)
---
Expected Behavior
- Scrolling should be non-destructive.
- All previously generated messages should remain intact and fully visible, regardless of scroll position.
- The chat history should render consistently without overwriting or clipping text.
---
Actual Behavior
- When scrolling up or down, parts of the message disappear (squash to non-existence?).
- Example: In the attached screenshot, everything after “Worked for 39s” is missing — multiple bullet points are clipped and unrecoverable.
- Asking Codex to regenerate or recall the message does not restore the exact original content, suggesting the original data is lost or unrendered.
---
Impact
- Severe: prevents users from reviewing or referencing past responses.
- Makes it impossible to debug or discuss complex issues in long Codex sessions.
- Reduces trust in conversation persistence and data integrity.
---
Attachments
- Screenshot 1: Clipped message after scrolling (shows truncation after “Worked for 39s”).
- Screenshot 2: Codex attempting to reconstruct the lost portion of the message.
---
Environment
- codex in Ghostty on macOS 15.7.2
Thread ID 019a63de-c2ab-7023-b482-f2d17522ccf0 in an existing
---
Severity
🔥 High — Loss of visible data and inability to retrieve prior messages.
25 Comments
Related to https://github.com/openai/codex/issues/2456
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Sometimes even new messages from the agent will cause content in the chat history to just clip and disappear.
I got it to reproduce by making AI print from 1 to 30.
#6599
are oai looking into this? thinking if wort switching back to iterm or not from ghostty. dont have the issue in iterm!
Using transcript mode might be an option. Use Ctrl+T
<img width="1040" height="608" alt="Image" src="https://github.com/user-attachments/assets/b31a807a-851c-461a-a017-5d8dbaa5d6d1" />
<img width="1040" height="612" alt="Image" src="https://github.com/user-attachments/assets/669e92b9-f2bf-4c90-93df-e8ae88e38aab" />
A simple reproduction method:
Scrolling the terminal will reveal that the /status command and its output status card disappear.
same issue
Same issue here.
I am facing the same issue. i am able to see the full text in the transcript but it is cut off in the normal chat mode.
Is this a joke or wtf is wrong with you devs?? 4 fcking months and this annoying bug is still happening, we are paying a service and you give us a SHIT app with a huge bug like this one and after months this is still not fixed... im starting to lose my mind with this garbage 5 years old kid dev bugs.
@etraut-openai terrible bug not happening on gemini cli or claude code... the only cli app with this novice bug is codex.
@etraut-openai keep hiding comments and marking this as "abuse" when your customers are waiting a fix for a simple bug from months ago.
@dhaern, we welcome feedback, but if you're going to post in this issue tracker, we ask that you be respectful and civil. Your comment above was inappropriate and over the line.
We have many users, many requests for bug fixes and features, and finite time. We prioritize our bug fixes and feature work based on where we can have the most impact.
If you want to contribute to this project, the code is open source, and we welcome RCAs (root cause analyses).
This is unnaceptable the text is truncating from months ago, this is a CRITICAL bug and we cant see the responses from the model, the severity of this bug is huge and this was reported months ago and NEVER happened in gemini cli, claude code or another CLIs. We are paying a suscription or API requests to OpenAI and you guys give us a tool with a huge bug like this and still you guys didnt fix this.
This is still happening and quite annoying. Long responses are impossible to read.
not sure if just me or not but this issue seems way worse with 0.99 version than before it, anyone else notice?
FYI - I just submitted a PR that fixes this: #11221
Just to chime in, this is driving me insane. It completely breaks workflows where you need to copy paste from one terminal to another, and is a gigantic usability regression. You can still see the text in transcript mode, but transcript copy paste won't let you highlight more than a screen's worth of text, so if you need to copy a response from the terminal, at trivial sizes it's going to be clipped (very easy to miss that there was a much longer response than you can see until you go to transcript) and then you have to go to transcript and very carefully "splice together the copy". It's really, really, really annoying.
update I haven't seen this since upgrading to v0.101.0
This! I face exactly the same issue as this.
Yeah after im the disrespectful after for saying the truth to @etraut-openai
I have been encountering this too. Here's an example:
<img width="1648" height="425" alt="Image" src="https://github.com/user-attachments/assets/d14770f8-a8f5-41d2-950f-97df9b1108aa" />
And a little later, after I asked for the previous steps to be relisted, it happened again:
<img width="1574" height="222" alt="Image" src="https://github.com/user-attachments/assets/57ec0050-7155-45b0-8593-c33957fe4541" />
I had that shit from months ago... even bad clis like Gemini dont have this bug, absolute pathetic from OpenAI
Are any of you still seeing this with the latest version (0.118.0)? We've rewritten big portions of the TUI since this bug was filed — and incorporated many bug fixes. It's quite possible that the issue no longer exists.
I stopped seeing this a while ago, but can't say when exactly it changed. Few weeks at least. Currently on 0.117.0 with Ghostty on Mac for context.
I'm still seeing this issue via xterm.js. it seems to occur most frequently on screen resize.
!Screenshot_20260407-105357.png