Skip to content

Long ChatGPT Desktop responses jump upward while scrolling #37849

Open

Description

@rasettastone-art

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

26.721.41059

What subscription do you have?

Free

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

On macOS Apple Silicon, long responses in the Codex/ChatGPT desktop app repeatedly jump/scroll upward while I am reading them. The bottom of the response becomes difficult or impossible to reach because the view moves back upward and leaves blank space below.
The issue has existed since I installed the app. I have already submitted Feedback twice, and the problem remains after two app updates.
The same conversations work normally in the browser/Safari.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019fec9e-445a-7012-8d03-31fb1a31bd31

What is the expected behavior?

when I write a question the text does not move up and up it just stays on the top level.

Additional information

No response

Activity

  1. github-actions commented on Aug 10, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  2. alias-pomelo commented on Aug 12, 2026

    @alias-pomelo

    Still reproducible in Codex/ChatGPT desktop app 26.803.61601 on macOS 26.5.2.

    A more specific trigger I am seeing: after I submit a prompt and the assistant finishes its reply, the whole conversation briefly flashes and jumps upward to the position of that prompt (often the beginning of that turn). This unexpected automatic scroll is visually jarring and breaks reading continuity.

    Steps to reproduce:

    1. Open a conversation with enough history to scroll.
    2. Submit a prompt and wait for the assistant response to complete.
    3. When the response finalizes, the viewport abruptly jumps back to the original user prompt.

    Expected: the viewport should remain anchored to the completed response/current reading position, with no post-completion jump or flash.

  3. oscarbrey commented on Aug 12, 2026

    @oscarbrey

    it was macOS 26.5.2, update

  4. rhys-vdw commented on Aug 15, 2026

    @rhys-vdw

    Same issues on Windows v 26.803.81509

    After finishing writing the answer the window scrolls up. The result is the new answer is cut off when it was previously entirely on-screen (it doesn't just scroll up because the in-progress answer is longer than the final answer).

  5. dmd commented on Aug 20, 2026

    @dmd

    I reproduce this with 26.814.41957 on MacOS Golden Gate PB4.

  6. lennylucas commented on Aug 27, 2026

    @lennylucas

    I still get this. Incredibly annoying.

  7. akurilin commented on Sep 1, 2026

    @akurilin

    Can confirm it's happening here too, latest macOS 26.6.2 with Codex pro. Makes it so that you have to wait for the full response to be generated before you can scroll down to read it, otherwise the scroll position will keep getting reset.

  8. jenss42 commented on Sep 4, 2026

    @jenss42

    If you want this fixed, use the feedback feature from the app.
    I'm struggeling with the same effect you are seeing, left feedback
    provided the link of this issue with the feedback
    #37849

  9. monterourena commented on Sep 20, 2026

    @monterourena

    Still occurring for me as of September 20, 2026 in the ChatGPT/Codex macOS desktop app. Responses jump upward unexpectedly and a very large empty area appears at the bottom of the conversation, making it difficult to read the complete response and maintain my reading position.

    Environment available for this report: macOS, arm64. My desktop client metadata identifies Codex Desktop/26.915.31945; the separate build number and exact macOS version have not been checked in About.

    This is a recurring problem during normal use, not just a preference about auto-scroll behavior. I also experience missing conversation sections, although I have not established whether that has the same cause as the scrolling/layout failure. I have not yet isolated a minimal trigger or tested the same affected conversation in Safari, so I am not claiming those specific comparisons from the original report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions