Responses in Codex cannot be scrolled through
Open 💬 6 comments Opened Mar 25, 2026 by jevin98
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.116.0
What subscription do you have?
pro
Which model were you using?
gpt-5.4
What platform is your computer?
Microsoft Windows NT 10.0.19044.0 x64
What terminal emulator and version are you using (if applicable)?
PowerShell, PowerShell 7, or CMD
What issue are you seeing?
-
What steps can reproduce the bug?
I have noticed that—regardless of whether I use PowerShell, PowerShell 7, or CMD—the responses previously generated within Codex Cli cannot be scrolled back up using the mouse to view the complete history; furthermore, duplicate content also appears.
What is the expected behavior?
<img width="2483" height="575" alt="Image" src="https://github.com/user-attachments/assets/d1d88f12-fa58-42d2-8c3d-40764f8cf0ba" />
It is evident that the content above is being displayed repetitively.
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
用win11 的终端 体验会好很多
Since there is currently a significant amount of data on my computer, I am concerned that upgrading might disrupt my work.
i'm using win 11 23H2 build, using in windows terminal, still the same
Solution found: This issue is caused by an outdated version of Windows Terminal.
I was using Windows Terminal v1.12, and scrolling in Codex was completely broken — mouse wheel did nothing, couldn't scroll up to see history at all.
After upgrading to Windows Terminal Preview v1.25, scrolling works perfectly in Codex.
Fix: Update Windows Terminal to the latest version (v1.14+ should work, as alternate scroll mode support was added in v1.14 via microsoft/terminal#3321).
You can install Windows Terminal Preview from the Microsoft Store, or download the latest release from GitHub.
Aside from the inability to embed it directly into the VS Code terminal, it's actually quite good.