WSL2 Ubuntu-26.04 terminal crashes after /exit #30133

Activity

1. github-actions

   assigned

   simonklee

   on May 31, 2026
2. github-actions commented on May 31, 2026

   

   github-actionsBot

   on May 31, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • TUI leaves terminal in mouse-reporting/raw mode; keystrokes / mouse events print as ^[[<... after exit or crash #10610: TUI leaves terminal in mouse-reporting/raw mode after exit or crash — describes the same symptom (broken terminal state, mouse events printing as escape sequences, keyboard not working properly) on WSL Ubuntu with xterm-256color terminal
3. gmedici

   added a commit that references this issue on Jun 16, 2026

   fix: TUI leaves terminal in mouse-reporting/raw mode; keystrokes / mo…

   ...

   9f37489
4. krflorian commented on Jul 20, 2026

   

   krflorian

   on Jul 20, 2026

   More actions

   the same is happening for me:

   Environment:

   • OpenCode version: v3.12.3
   • OS: Windows with WSL (Ubuntu)
   • Terminal: Windows Terminal
   • Shell: WSL bash/zsh

   Description:
   After closing OpenCode, the terminal continuously outputs escape sequences like:
   35;112;43M35;111;42M35;110;41M...
   This does not stop even with Ctrl+C. Running reset fixes it.

   Root cause (suspected):
   OpenCode enables mouse tracking (SGR mouse reporting) for its UI. When the
   process exits via window close or abnormal termination, the disable sequence
   (\x1b[?1000l) is not sent to the terminal. With Windows Terminal + WSL, the
   raw mouse sequences are then fed into WSL's stdin as keyboard input.

   Steps to reproduce:

   1. Open Windows Terminal with a WSL pane
   2. Launch OpenCode from Windows (not from within WSL)
   3. Close OpenCode abruptly (Ctrl+C or close window)
   4. Observe terminal flooding with M35;... sequences

   Expected: Terminal state is reset on exit
   Workaround: Run reset in the affected terminal pane

   👍React with 👍1Reacted by Ilya
5. github-actions commented on Sep 19, 2026

   

   github-actionsBot

   on Sep 19, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
6. github-actions

   closed this as not plannedon Sep 19, 2026