TUI leaves terminal in mouse-reporting/raw mode; keystrokes / mouse events print as ^[[<... after exit or crash #10610

Description

Summary

After running opencode, my terminal sometimes ends up “stuck” in a broken state where input behaves incorrectly and mouse events / keystrokes print directly into the shell prompt (ex: ^[[<35;62;19M). This looks like the TUI enables mouse reporting / raw mode and doesn’t always restore terminal settings on exit/crash.

What happens

• The TUI appears to “break” and input starts going outside of the UI.

• After quitting or killing opencode, the terminal remains messed up:

  • Clicking/scrolling prints escape sequences like:

    ^[[<35;62;19M
    

    (This matches xterm SGR mouse reporting: ESC [ < b ; x ; y M)

  • Shell input becomes unusable until terminal is reset.

Expected behavior

When opencode exits (even after unexpected termination), terminal settings should be restored so the shell behaves normally.

Reproduction steps

1. Run:

Unable to reproduce consistently. Opencode crash causes issue. I have to close the terminal to stop it.

Evidence / screenshot

After the issue triggers, the terminal prints sequences like:

^[[<35;62;19M ...

Environment

• opencode version: 1.1.36
• node: v24.12.0
• bun: 1.3.6
• TERM: xterm-256color
• OS: Ubuntu WSL on Windows 11
• Install method: bun global install

Notes / suspicion

This looks like terminal modes (raw input + mouse reporting) aren’t being cleaned up on some exit paths (crash, hang, SIGKILL, or parent/child process exit mismatch). The launcher process (node .../opencode) + native binary process might have separate lifecycle/TTY handling, leaving the terminal in mouse-reporting mode.

Plugins

No response

OpenCode version

1.1.36

Steps to reproduce

No response

Screenshot and/or share link

Operating System

Ubuntu 20.04.6 LTS (Focal Fossa) / WSL Windows 11

Terminal

vscode terminal bash