openai / openai/codex

PageUp / PageDown do not reliably scroll the current conversation in Codex App on Windows

Open
#41,782 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug enhancement windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App

What feature would you like to see?

In the Windows version of the Codex App / ChatGPT Desktop App, pressing PageUp or PageDown does not reliably scroll the current conversation. The official keyboard shortcut docs mention Ctrl + PageUp / Ctrl + PageDown for switching to the previous or next chat/tab, but plain PageUp / PageDown do not seem to consistently work for scrolling the active conversation pane.

Environment

  • OS: Windows
  • App: Codex App / ChatGPT Desktop App
  • Keyboard: Standard keyboard with dedicated PageUp / PageDown keys

Steps to Reproduce

  1. Open a long conversation in Codex App.
  2. Click inside the conversation/content area, or leave the default focus as-is.
  3. Press PageUp or PageDown.
  4. Observe whether the current conversation scrolls by page.

Actual Behavior
PageUp / PageDown do not reliably scroll the current conversation. In some cases, the key event appears to be swallowed by the input box, terminal, code panel, browser panel, or another focused area.
Expected Behavior
When the conversation pane is focused, or when there is no active text-input focus, PageUp / PageDown should scroll the current conversation just like in standard browsers and desktop applications.
Additional Context
Ctrl + PageUp / Ctrl + PageDown can remain mapped to previous/next chat or tab switching. This request is specifically about supporting plain PageUp / PageDown for scrolling the active content pane on Windows.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reproducing the PageUp/PageDown behavior in a long Windows conversation, then trace the desktop app's keyboard-focus and conversation-scrolling entry points; done means plain PageUp/PageDown scroll the active conversation without breaking input, terminal, code-panel, browser-panel, or Ctrl-based tab switching.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.