Codex app enters an infinite scroll loop after using the jump-to-bottom button

Open 💬 3 comments Opened Jun 17, 2026 by Aesthermortis

https://github.com/user-attachments/assets/4733e283-92a3-4dfa-9fda-de54150d2719

Description

When opening an existing long session, the conversation sometimes remains at or restores to an incorrect position near the beginning instead of the latest message.

Pressing the down-arrow / jump-to-bottom button can then put the session into an infinite scroll loop.

The viewport repeatedly alternates between:

  • an earlier section of the conversation;
  • the latest section of the conversation;
  • a blank area where the conversation content temporarily disappears.

The loop continues without any additional user input and makes the session unusable.

I attached a video showing the full behavior.

Steps to reproduce

  1. Open an existing long Codex session.
  2. Wait for the conversation to load.
  3. If the session remains at an earlier position, press the down-arrow button to jump to the latest message.
  4. Observe the viewport.

Actual behavior

The app repeatedly jumps between different positions in the conversation and a blank viewport.

The jump-to-bottom action does not settle at the latest message and instead triggers a continuous scrolling or rendering loop.

Expected behavior

Pressing the jump-to-bottom button should:

  1. scroll to the latest message once;
  2. render the conversation normally;
  3. stop scrolling without further movement.

Frequency

Intermittent. It does not happen every time a session is opened, but once triggered, the loop continues repeatedly.

Additional observations

  • The issue appears more likely in long sessions.
  • The blank state suggests that conversation items may be temporarily unmounted or incorrectly positioned while the scroll location is being restored.
  • It may involve an interaction between session scroll restoration, automatic scrolling, and conversation list virtualization.
  • This is only a possible explanation based on the visible behavior; I have not confirmed the underlying cause.

Environment

  • Codex app
  • Operating system: Windows
  • Session type: existing long conversation

The attached video provides the clearest reproduction of the issue.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗