Selecting text during an active response results in unresponsive UI #2876

Closed
opened 2026-02-16 17:37:38 -05:00 by yindo · 9 comments
Owner

Originally created by @zkdiff on GitHub (Nov 15, 2025).

Originally assigned to: @kommander on GitHub.

Description

OS: macOS Tahoe
Terminal: Ghostty

OpenCode version

v1.0.63

Steps to reproduce

  1. launch opencode in the ghostty terminal
  2. input "what is your name?" in the message box
  3. submit message and begin selecting text in the chat log
  4. continue the selection until the screen scrolls
  5. observe the console automatically appear, take focus, and all interaction freeze.

the agent continues to update files and everything... it is just the TUI that hangs

Screenshot and/or share link

Image

Operating System

macos tahoe 26.1

Terminal

Ghostty

Originally created by @zkdiff on GitHub (Nov 15, 2025). Originally assigned to: @kommander on GitHub. ### Description OS: macOS Tahoe Terminal: Ghostty ### OpenCode version v1.0.63 ### Steps to reproduce 1. launch opencode in the ghostty terminal 2. input "what is your name?" in the message box 3. submit message and begin selecting text in the chat log 4. continue the selection until the screen scrolls 5. observe the console automatically appear, take focus, and all interaction freeze. the agent continues to update files and everything... it is just the TUI that hangs ### Screenshot and/or share link <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/a26a9ccc-9a91-4836-b464-419138b0a647" /> ### Operating System macos tahoe 26.1 ### Terminal Ghostty
yindo added the opentuibug labels 2026-02-16 17:37:38 -05:00
yindo closed this issue 2026-02-16 17:37:38 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 15, 2025):

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

  • #3627: Similar text selection behavior issues in opentui with terminal emulators
  • #3846: UI becoming unresponsive to user input, also reported with Ghostty terminal
  • #2037: Ghostty-specific issue with mouse interaction causing unwanted highlighting behavior
  • #3695: Mouse event handling problems in the new TUI (opentui)

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

@github-actions[bot] commented on GitHub (Nov 15, 2025): This issue might be a duplicate of existing issues. Please check: - #3627: Similar text selection behavior issues in opentui with terminal emulators - #3846: UI becoming unresponsive to user input, also reported with Ghostty terminal - #2037: Ghostty-specific issue with mouse interaction causing unwanted highlighting behavior - #3695: Mouse event handling problems in the new TUI (opentui) Feel free to ignore if none of these address your specific case.
Author
Owner

@zkdiff commented on GitHub (Nov 15, 2025):

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

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

These are kinda similar but not exactly

@zkdiff commented on GitHub (Nov 15, 2025): > This issue might be a duplicate of existing issues. Please check: > > * [opentui: weird text selection behavior in wezterm #3627](https://github.com/sst/opencode/issues/3627): Similar text selection behavior issues in opentui with terminal emulators > * [No response to user input #3846](https://github.com/sst/opencode/issues/3846): UI becoming unresponsive to user input, also reported with Ghostty terminal > * [[bug] ghostty/arch | moving the mouse over the terminal content highlights it as if you're click-dragging #2037](https://github.com/sst/opencode/issues/2037): Ghostty-specific issue with mouse interaction causing unwanted highlighting behavior > * [The new TUI cannot handle mouse events #3695](https://github.com/sst/opencode/issues/3695): Mouse event handling problems in the new TUI (opentui) > > Feel free to ignore if none of these address your specific case. These are kinda similar but not exactly
Author
Owner

@rekram1-node commented on GitHub (Nov 16, 2025):

we will fix thanks for raising

@rekram1-node commented on GitHub (Nov 16, 2025): we will fix thanks for raising
Author
Owner

@veracioux commented on GitHub (Nov 17, 2025):

@rekram1-node Looks similar to https://github.com/sst/opencode/issues/4099. I have an opentui PR for this. I think it should be fixed by that.

@veracioux commented on GitHub (Nov 17, 2025): @rekram1-node Looks similar to https://github.com/sst/opencode/issues/4099. I have an opentui PR for this. I think it should be fixed by that.
Author
Owner

@rekram1-node commented on GitHub (Nov 17, 2025):

prolly related yeah

@rekram1-node commented on GitHub (Nov 17, 2025): prolly related yeah
Author
Owner

@veracioux commented on GitHub (Nov 19, 2025):

@kommander @rekram1-node I'm quite confident this will be fixed by https://github.com/sst/opentui/pull/285

Can't reproduce using the exact steps as OP, but I can reliably reproduce an identical stack trace using the following steps:

  1. Open model dialog
  2. Select some text in it (keep mouse pressed for next steps)
  3. Close dialog using esc (still holding mouse pressed)
  4. Move the mouse (still pressed)
@veracioux commented on GitHub (Nov 19, 2025): @kommander @rekram1-node I'm quite confident this will be fixed by https://github.com/sst/opentui/pull/285 Can't reproduce using the exact steps as OP, but I can reliably reproduce an identical stack trace using the following steps: 1. Open model dialog 2. Select some text in it (keep mouse pressed for next steps) 3. Close dialog using esc (still holding mouse pressed) 4. Move the mouse (still pressed)
Author
Owner

@kommander commented on GitHub (Nov 19, 2025):

The PR by @veracioux is merged and released with opentui and should be in the upcoming v1.0.79 version of opencode, fixing this.

@kommander commented on GitHub (Nov 19, 2025): The PR by @veracioux is merged and released with opentui and should be in the upcoming v1.0.79 version of opencode, fixing this.
Author
Owner

@rekram1-node commented on GitHub (Nov 19, 2025):

released, should be fixed

@rekram1-node commented on GitHub (Nov 19, 2025): released, should be fixed
Author
Owner

@zkdiff commented on GitHub (Nov 19, 2025):

awesome, thanks!

Tested and verified fix with 1.0.80

@zkdiff commented on GitHub (Nov 19, 2025): awesome, thanks! Tested and verified fix with 1.0.80
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2876