fix(tui): disable mouse tracking on exit to prevent terminal corruption

[d-init-d]

Fixes#6912

Problem

When pressing Ctrl+C to exit OpenCode on Windows, the terminal is left in mouse tracking mode. This causes raw SGR mouse tracking escape sequences to flood the terminal on every mouse movement, rendering the terminal unusable:

[555;58;25M[555;58;26M[555;57;25M[555;57;24M...

The issue occurs because:

1. SIGINT handler wasn't properly cleaning up terminal state
2. process.exit(0) was called before cleanup sequences could be flushed
3. The async nature of renderer.destroy() meant sequences might not reach the terminal

Solution

Added synchronous terminal cleanup using fs.writeSync() to ensure ANSI disable sequences are written immediately before process exit:

• cleanupTerminal() - Synchronously writes disable sequences directly to stdout (fd 1)
• destroyRenderer() - Exported function for SIGINT handler to properly cleanup
• SIGINT handler - Registered in tui() to catch Ctrl+C and call cleanup

ANSI Sequences Covered

The fix disables all common mouse tracking modes:

Sequence	Mode
\x1b[?1000l	X11 mouse tracking (button press/release)
\x1b[?1002l	Button-event tracking (press/release/motion with button)
\x1b[?1003l	Any-event tracking (all motion)
\x1b[?1006l	SGR extended mouse mode
\x1b[?1015l	URXVT extended mouse mode
\x1b[?25h	Show cursor

Changes

• packages/opencode/src/cli/cmd/tui/context/exit.tsx:

  • Added cleanupTerminal() for synchronous cleanup
  • Added destroyRenderer() export for external use
  • Call cleanup before renderer.destroy()

• packages/opencode/src/cli/cmd/tui/app.tsx:

  • Import destroyRenderer from exit context
  • Register SIGINT handler in tui() function
  • Update ErrorComponent to use destroyRenderer()

Testing

1. Run bun dev or opencode
2. Press Ctrl+C to exit
3. Mouse movements should NOT produce escape sequence output
4. Terminal should be in normal state

Related Issues

• FixesCtrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) #6912 - Ctrl+C does not disable mouse tracking (Windows)
• Related to In version 1.1.23, the issue of the mouse wheel triggering abnormal ASCII codes after exiting reappeared. #8908 - Mouse wheel triggering abnormal ASCII codes after exit
• Related to macOS: Terminal becomes unusable after opencode exits ("dead terminal") #7861 - Terminal becomes unusable after opencode exits (macOS)

Note

This PR provides a similar fix to #8355 but with improvements:

• More comprehensive ANSI sequences coverage
• Better code organization with JSDoc comments
• Consistent cleanup across all exit paths (normal exit, Ctrl+C, error component)

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate/Related PRs Found:

1. PR fix(opencode): disable mouse tracking on exit #8355 - fix(opencode): disable mouse tracking on exit

   • fix(opencode): disable mouse tracking on exit #8355
   • Reason: Directly related - the current PR (fix(tui): disable mouse tracking on exit to prevent terminal corruption #11019) explicitly mentions it provides a similar fix with improvements

2. PR fix(opentui): handle SIGINT to prevent garbled output on Windows #10433 - fix(opentui): handle SIGINT to prevent garbled output on Windows

   • fix(opentui): handle SIGINT to prevent garbled output on Windows #10433
   • Reason: Addresses the same root cause (SIGINT handler and terminal cleanup on Windows) to prevent garbled output

Both PRs are tackling the same underlying issue with terminal state cleanup on exit, particularly on Windows. The current PR (#11019) appears to be a more comprehensive solution compared to PR #8355 with better ANSI sequence coverage and improved code organization.

[github-actions]

Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR.