After exiting opencode, there is residual output left on the screen. #8591

Open
opened 2026-02-16 18:10:20 -05:00 by yindo · 1 comment
Owner

Originally created by @bye-byte on GitHub (Feb 5, 2026).

Originally assigned to: @kommander on GitHub.

Question

I am currently using the Alacritty + Tmux + Fish. After exiting opencode, there is residual output left on the screen. How can I resolve this issue?

Image
Originally created by @bye-byte on GitHub (Feb 5, 2026). Originally assigned to: @kommander on GitHub. ### Question I am currently using the Alacritty + Tmux + Fish. After exiting opencode, there is residual output left on the screen. How can I resolve this issue? <img width="1091" height="315" alt="Image" src="https://github.com/user-attachments/assets/3e3dac09-8f29-4904-b334-4ecc742f91d0" />
yindo added the opentui label 2026-02-16 18:10:20 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 5, 2026):

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

  • #7861: macOS: Terminal becomes unusable after opencode exits ("dead terminal")
  • #5936: Random Artifacts In Terminal After Running
  • #6912: Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows)
  • #5070: bug: exiting tui on windows has improper exit sequence handling
  • #12044: An unknown string is displayed loop when closing the OpenCode CLI
  • #10719: Terminal state not restored when exiting with ctrl+c on windows (git bash)
  • #9557: When I press Esc to exit OpenCode, it fails to open and keeps printing
  • #7600: Unexpected Error when exit Opencode from terminal (Alacritty)
  • #11433: Cursor does not reset in some terminals
  • #8484: Screen lag/freezing when typing text (WSL2, TMUX, Alacritty)
  • #10867: [Bug][WSL][tmux]: Cannot be interrupted by ESC

These issues appear to be related to a broader terminal cleanup/exit sequence handling problem affecting multiple platforms and terminal configurations.

Feel free to ignore if your specific case is different.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #7861: macOS: Terminal becomes unusable after opencode exits ("dead terminal") - #5936: Random Artifacts In Terminal After Running - #6912: Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) - #5070: bug: exiting tui on windows has improper exit sequence handling - #12044: An unknown string is displayed loop when closing the OpenCode CLI - #10719: Terminal state not restored when exiting with ctrl+c on windows (git bash) - #9557: When I press Esc to exit OpenCode, it fails to open and keeps printing - #7600: Unexpected Error when exit Opencode from terminal (Alacritty) - #11433: Cursor does not reset in some terminals - #8484: Screen lag/freezing when typing text (WSL2, TMUX, Alacritty) - #10867: [Bug][WSL][tmux]: Cannot be interrupted by ESC These issues appear to be related to a broader terminal cleanup/exit sequence handling problem affecting multiple platforms and terminal configurations. Feel free to ignore if your specific case is different.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8591