Conversation pane does not support reliable keyboard scrolling

What version of the Codex App are you using (From “About Codex” dialog)?

26.429.30905

What subscription do you have?

Plus

What platform is your computer?

Windows 11 x64

What issue are you seeing?

Codex Desktop on Windows does not reliably allow scrolling through long conversations using standard keyboard navigation.

When a Codex session becomes long, it is difficult to review previous messages, command output, diffs, errors, and intermediate explanations because the conversation/history pane does not respond properly to keyboard scrolling shortcuts.

This is an accessibility and usability issue, especially for users who rely on keyboard navigation or have difficulty with precise mouse interaction.

In long Codex conversations, the conversation/history pane does not scroll reliably using standard keyboard navigation.

The following keys either do not work, do not work consistently, or do not target the correct scrollable area:

• Up Arrow
• Down Arrow
• Page Up
• Page Down
• Home
• End
• Space
• Shift+Space

As a result, reviewing long sessions requires relying on the mouse wheel or scrollbar instead of normal keyboard navigation.

This is especially problematic because Codex sessions often contain many commands, tool calls, diffs, validation results, and intermediate messages. If those messages scroll out of view, it becomes difficult to go back and read them comfortably.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.
2. Open or create a long Codex session with enough content to require vertical scrolling.
3. Click or focus the conversation/history pane.
4. Try to scroll the conversation using:

• Up Arrow
• Down Arrow
• Page Up
• Page Down
• Home
• End
• Space
• Shift+Space

1. Observe that keyboard scrolling does not work reliably or does not target the conversation/history pane correctly.

What is the expected behavior?

The conversation/history pane should support reliable keyboard scrolling when it is visible and focused.

• Up Arrow should scroll the conversation/history pane upward.
• Down Arrow should scroll the conversation/history pane downward.
• Page Up should scroll upward by approximately one page.
• Page Down should scroll downward by approximately one page.
• Home should jump to the beginning of the focused scrollable conversation area.
• End should jump to the end of the focused scrollable conversation area.
• Space should scroll downward by approximately one page.
• Shift+Space should scroll upward by approximately one page.

These shortcuts should apply when focus is on the conversation/history area.

They should not interfere with typing in the prompt box, nor with focused buttons, menus, text inputs, or other interactive controls.

Additional information

This is not just a convenience issue. It affects accessibility and basic usability.

This should be treated as an accessibility bug, not only as a feature request. Keyboard scrolling is expected behavior in long scrollable content, especially in a developer tool where users often need to review lengthy command output and conversation history.