Codex desktop viewport jumps and composer overlays text while user is reading scrolled history

Summary

When reading a Codex desktop task while scrolled above the bottom, the conversation viewport repeatedly jumps/reflows without user input. The floating composer also overlays message content instead of reserving vertical space, hiding the text the user is trying to read.

This happened repeatedly in one task while the user was reading prior assistant messages. The user was not interacting with the input/composer when at least one jump occurred.

Environment

• App: Codex desktop / ChatGPT Windows Store package
• Package: OpenAI.Codex_26.803.10989.0_x64__2p2nqsd0c76g0
• Version: 26.803.10989.0
• SignatureKind: Store
• OS: Windows, user environment path indicates Windows desktop

Steps to reproduce

1. Open a long Codex task with enough messages to scroll.
2. Scroll upward to read prior assistant text, not at the bottom.
3. Continue reading while the task/composer is idle, or while new nearby content/layout settles.
4. Observe the viewport unexpectedly jump/reflow.
5. Observe the composer overlaying the message area and hiding text behind the input box.

Actual behavior

• Reading position is not preserved while scrolled above the bottom.
• The viewport jumps/reflows repeatedly.
• The bottom composer overlays readable message content.
• Text being read is pushed under/behind the composer.
• A jump-to-bottom affordance is visible, but the app still changes the viewport while the user is reading.

Expected behavior

• If the user is scrolled above the bottom, preserve the scroll anchor.
• Do not auto-scroll/reflow the viewport unless the user explicitly jumps to bottom or is already at bottom.
• Reserve bottom padding/layout space equal to the composer height.
• Never allow the composer to cover message text.
• If new messages/content arrive while the user is scrolled up, show a non-disruptive “new message” affordance.

Suggested implementation direction

• Track whether the scroll container is near bottom before content/composer size changes.
• If not near bottom, preserve the currently visible message/scroll anchor through layout changes.
• If near bottom, continue auto-scroll behavior.
• Ensure the message list has bottom padding equal to the composer height rather than relying on overlay behavior.

Pseudo behavior:

const wasAtBottom = isNearBottom(scrollContainer)

onContentOrComposerResize(() => {
  if (wasAtBottom) scrollToBottom()
  else preserveScrollAnchor()
})

Screenshots captured locally

The user provided screenshots showing the composer covering message text and the reading viewport jumping:

• C:/Users/mattr/AppData/Local/Temp/codex-clipboard-1cdf1cbd-35da-41ad-a1d7-84bc85ec9905.png
• C:/Users/mattr/AppData/Local/Temp/codex-clipboard-e1f7a3ab-068b-4a33-b6ec-b6406e859f6c.png
• C:/Users/mattr/AppData/Local/Temp/codex-clipboard-9591ef57-eb5b-4b3c-96fe-49357eb7f09a.png

I cannot attach those local files through this connector, but they demonstrate the issue clearly: the composer floats over the lower message text while the user is scrolled up and reading.

Start by reproducing the issue in a long Codex desktop task while scrolled above the bottom, then trace the conversation viewport, message list, and floating composer scroll and resize handling. Done means the reading anchor stays stable during content or composer changes, the composer never covers message text, and near-bottom behavior still supports explicit jump-to-bottom actions.