[Windows] Hard-killed TUI leaves mouse reporting enabled; next launch does not reset terminal state

[janah01]

Description

When the TUI is force-killed externally on Windows, the terminal can be left with mouse reporting enabled. After that, moving the mouse floods the prompt with raw escape sequences such as ^[[<35;62;19M. Relaunching opencode does not clear it, because the new renderer inherits the terminal's dirty state.

This is different from #6912 and #13301, which are about Ctrl+C cleanup. With taskkill /F, the process gets no chance to run exit handlers.

Possible fix: disable mouse tracking on TUI startup before enabling it again.

Plugins

none

OpenCode version

1.3.0

Steps to reproduce

1. Launch opencode in Windows Terminal (PowerShell)
2. Force-kill it with taskkill /F /PID <pid>
3. Move the mouse in the terminal — raw escape sequences appear
4. Relaunch opencode
5. Move the mouse again — raw escape sequences still appear

Operating System

Windows 11

Terminal

Windows Terminal (PowerShell)

[github-actions]

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

• After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the powershell will cause garbled characters. #11748: Same symptom on Windows - mouse movement/scrolling causes garbled characters after closing OpenCode CLI in PowerShell
• In version 1.1.23, the issue of the mouse wheel triggering abnormal ASCII codes after exiting reappeared. #8908: Same symptom on Windows 11 - mouse wheel triggers abnormal ASCII codes after exiting via Ctrl+C
• bug: exiting tui on windows has improper exit sequence handling #5070: Windows TUI exit leaves mouse escape sequences in terminal (git bash)

Note: The author already distinguishes this from #13301 (Ctrl+C) — the key difference here is taskkill /F with no exit handlers. If the underlying fix is the same (reset mouse tracking on startup), these may still be related enough to consolidate.