Skip to content

Setting to prevent TUI scrolling when new message are streamed-in #7648

Closed as not planned

Description

@alexx-ftw

Title is self-explanatory.
I like to read TUI messages while the Agent is working and streaming-in new messages below, but the current behavior of scrolling down is a bit annoying.

I searched for and didn't find any setting that controls that.

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Jan 10, 2026
  2. github-actions commented on Jan 10, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  3. alexx-ftw commented on Jan 10, 2026

    @alexx-ftw
    Author

    I have implemented this feature in PR #7651. You can now disable auto-scrolling by setting tui.auto_scroll to false in your config.

  4. JuliaBonita commented on Jan 11, 2026

    @JuliaBonita

    Ideally, this feature would be intelligent enough to disable auto-scroll only when the user has intentionally scrolled up from the bottom of the window. This is how many other LLM chat interfaces work. That way, if the current scroll position is at the bottom of the stream, then the auto-scroll will stay active because it's safe to assume the user wants to see the real-time stream. But if the user has moved the scroll position to a previous point in the stream, then the assumption should be that the user wants auto-scroll to be disabled.

  5. JuliaBonita commented on Feb 12, 2026

    @JuliaBonita

    This issue does not seem to happen when using Kimi K2.5, but it happens constantly with Claude. So it appears this is caused by how OC is interpreting and rendering Claude's (and mabye other models) specific responses. I notice that Kimi K2.5 streams its responses a bit differently; so it should be easy to visually see the difference.

  6. jcontini commented on Feb 24, 2026

    @jcontini

    +1

    Toggled scrollbars on, it still jumps down on tool completions. My eyes...they hurt

  7. stee-re commented on Mar 28, 2026

    @stee-re

    yes, I agree - this automatic scrolling down when the AI response changes makes this tool a little frustrating to use - I'm being forced to wait for some lengthy responses (so often a lot more than I wanted) until the Agent is completely finished. Then I can begin reading the response. It makes the process so much slower :-(

    Otherwise - TOTALLY LOVING this tool - really really awesome work guys

  8. John-Gee commented on Apr 11, 2026

    @John-Gee

    I'm having this issue with minimax, I'm not sure why the model should matter though here...

  9. kreasteve commented on Apr 18, 2026

    @kreasteve

    Looked at the source with Claude — turns out you can just add

    "mouse": true

    to ~/.config/opencode/tui.json so it looks like this (create the file if needed):

    {
      "$schema": "https://opencode.ai/tui.json",
      "mouse": true
    }

    Restart opencode and it works.

    Tested with MiniMax-M2.5 on macOS in iTerm2 — does exactly what's asked for in this issue: scroll up (wheel or PageUp) pauses sticky, scroll back to the bottom resumes it.


    Edit: On closer testing I can't actually reproduce the bug without the file either — mouse defaults to true and the desired behavior already works. So this might not be the actual fix. Sorry for the noise.

  10. removed
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on May 3, 2026
  11. github-actions commented on Jul 16, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

  12. davispuh commented on Aug 18, 2026

    @davispuh

    This has been annoying me so much. I just want to read and not having to keep scrolling back up all the time.

  13. davispuh commented on Aug 18, 2026

    @davispuh

    There's open duplicate #29094 and looks like will get solved with #40323

  14. nullbio commented on Aug 24, 2026

    @nullbio

    Insane that this is still an issue. Reminds me of Claude Code, they had this bug for, what, a whole year?

  15. diegorodriguezv commented on Oct 10, 2026

    @diegorodriguezv

    yes, please fix this

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions