Codex output panel keeps jumping up and down continuously

Open 💬 3 comments Opened Jun 23, 2026 by Tompomelo15612
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.616.71553

What subscription do you have?

plus

What platform is your computer?

windows11

What issue are you seeing?

I am experiencing a UI issue in the Codex desktop app.

When Codex is generating or displaying output, the output panel repeatedly jumps or scrolls up and down by itself. The page continuously moves vertically without any mouse wheel or keyboard input.

This makes the generated content difficult to read, review, copy, select, or interact with.

Expected behavior:
The output panel should remain stable while Codex is generating or displaying content, unless I manually scroll.

Actual behavior:
The output panel continuously jumps upward and downward automatically.

Frequency:
[Choose one: Happens every time / Happens frequently / Happened once]

I have attached a screen recording showing the issue.

<!-- Failed to upload "屏幕录制 2026-06-23 224423.mp4" -->

What steps can reproduce the bug?

Feedback ID: 019ef4cc-78ee-7083-b443-f6a740170d0f

What is the expected behavior?

I am experiencing a UI issue in the Codex desktop app.

When Codex is generating or displaying output, the output panel repeatedly jumps or scrolls up and down by itself. The page continuously moves vertically without any mouse wheel or keyboard input.

This makes the generated content difficult to read, review, copy, select, or interact with.

Expected behavior:
The output panel should remain stable while Codex is generating or displaying content, unless I manually scroll.

Actual behavior:
The output panel continuously jumps upward and downward automatically.

Frequency:
[Choose one: Happens every time / Happens frequently / Happened once]

I have attached a screen recording showing the issue.

<!-- Failed to upload "屏幕录制 2026-06-23 224423.mp4" -->

Additional information

none

View original on GitHub ↗

3 Comments

Tompomelo15612 · 2 months ago

<!-- Failed to upload "屏幕录制 2026-06-23 224423.mp4" -->

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #28718
  • #28755

Powered by Codex Action

andy820621 · 1 month ago

I am experiencing the same issue on macOS after updating the ChatGPT desktop app today.

Environment

  • App: ChatGPT desktop app, powered by Codex & OWL
  • App version: 26.707.31428
  • App release date shown in About dialog: Jul 10, 2026
  • Operating system: macOS 26.5.2
  • macOS build: 25F84
  • CPU architecture: arm64
  • In-app Feedback ID: 019f49b7-8c97-7460-a7eb-a3f06d1ecc8c

Actual behavior

While Codex is running a task and generating or displaying output, the
conversation viewport intermittently jumps back and forth between two vertical
scroll positions.

This happens without any mouse-wheel, trackpad, scrollbar, or keyboard input.
The message composer remains fixed, while the conversation content repeatedly
moves up and down by itself.

Once triggered, the behavior makes it difficult to read or review the current
output.

Expected behavior

The conversation viewport should remain stable while output is being generated
or displayed.

It should remain anchored to the current scroll position, or follow the latest
output, unless I manually scroll.

Frequency

Intermittent. It does not happen during every task, but it has occurred multiple
times since updating to version 26.707.31428.

Regression

I first noticed this behavior immediately after updating the app on July 10,
2026.

Additional information

  • I already submitted an in-app feedback report from an affected session.
  • Feedback ID: 019f49b7-8c97-7460-a7eb-a3f06d1ecc8c
  • A screen recording showing the behavior is attached.
  • No mouse, trackpad, keyboard, or scrollbar input was being made while the

viewport was moving.

  • This appears to match the issue described here, but it is also occurring on

macOS with app version 26.707.31428.