After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the powershell will cause garbled characters. #11748

Activity

1. FYZAFH

   added

   bugSomething isn't workingSomething isn't working

   on Feb 2, 2026
2. FYZAFH

   changed the title [-]After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the command line will cause garbled characters.[/-] [+]After closing the OpenCode CLI, scrolling the mouse wheel and moving the mouse in the powershell will cause garbled characters.[/+] on Feb 2, 2026
3. github-actions

   assigned

   kommander

   on Feb 2, 2026
4. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   windows

   on Feb 2, 2026
5. github-actions commented on Feb 2, 2026

   

   github-actionsBot

   on Feb 2, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • The terminal displays garbled characters. #10951: The terminal displays garbled characters (after exiting with /exit command)
   • In version 1.1.23, the issue of the mouse wheel triggering abnormal ASCII codes after exiting reappeared. #8908: In version 1.1.23, the issue of the mouse wheel triggering abnormal ASCII codes after exiting reappeared (very similar symptoms with mouse wheel in PowerShell after Ctrl+C exit)
   • OpenCode crashes during use on Windows (garbled console output) #10414: OpenCode crashes during use on Windows (garbled console output)
   • Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text #7062: Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text

   The issue appears to be related to terminal state cleanup on Windows when exiting OpenCode, particularly with PowerShell and mouse/scroll input interactions.

   Feel free to ignore if none of these address your specific case.

   👍React with 👍1Reacted by LuncyBloont
6. cobbvanth commented on Feb 26, 2026

   

   cobbvanth

   on Feb 26, 2026

   More actions

   Yep I've got this issue too

   👍React with 👍1Reacted by LuncyBloont
7. LuncyBloont commented on Mar 7, 2026

   

   LuncyBloont

   on Mar 7, 2026

   More actions

   Same. And windows terminal is OK, but VS Code terminal can't handle mouse scroll after exit opencode. Git bash is same and push garbled characters.
8. FYZAFH commented on Mar 7, 2026

   

   FYZAFH

   on Mar 7, 2026

   Author

   More actions

   I originally wanted to try OpenCode, but I got stuck on this bug, which makes it completely unusable. I didn’t expect that more than a month has passed and it still hasn’t been fixed.

   Same. And windows terminal is OK, but VS Code terminal can't handle mouse scroll after exit opencode. Git bash is same and push garbled characters.
9. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   windows

   on May 3, 2026
10. samuel-pro-ai commented on Jun 12, 2026

    

    samuel-pro-ai

    on Jun 12, 2026

    Last edited by samuel-pro-ai

    More actions

    Can confirm this is still happening on v1.17.3 (latest) with WSL Ubuntu + VS Code integrated terminal.

    Reproduction:

    1. Launch opencode in VS Code's integrated terminal (default profile: Ubuntu WSL)
    2. Exit via built-in /exit command
    3. Move the mouse over the terminal
    4. Terminal spams: 35;75;9M35;72;8M35;70;8M... continuously

    The terminal becomes unusable for typing until the VS Code terminal panel is closed and reopened. reset, stty sane, and printf '\e[?1006l' all do not clear the buffered escape sequences.

    Workaround: OPENCODE_DISABLE_MOUSE=1 works but kills mouse support inside the TUI.

    This is a blocker for anyone using opencode inside VS Code + WSL.

    👀React with 👀1Reacted by Emaia
11. mmuqiitf commented on Jun 24, 2026

    

    mmuqiitf

    on Jun 24, 2026

    More actions

    No updates (?)
12. emaia commented on Jul 7, 2026

    

    emaia

    on Jul 7, 2026

    More actions

    Same problem here (terminal spams) on v1.17.14 + wsl v2.7.10 + windows terminal. Not using vscode.
13. HaoXiongDev commented on Aug 7, 2026

    

    HaoXiongDev

    on Aug 7, 2026

    Last edited by HaoXiongDev

    More actions

    The iuess still exists in the opencode Version: 1.18.14.

    WSL version: 2.7.10.0
    Core version: 6.18.33.2-2
    WSLg version: 1.0.73.2
    MSRDC version: 1.2.6676
    Direct3D version: 1.611.1-81528511
    DXCore version: 10.0.26100.1-240331-1435.ge-release
    Windows: 10.0.26100.4349
    

    
14. EvilBeaver commented on Aug 14, 2026

    

    EvilBeaver

    on Aug 14, 2026

    More actions

    Same on Unbuntu in ssh sessions
15. hoegge commented on Sep 23, 2026

    

    hoegge

    on Sep 23, 2026

    More actions

    For me it is not the case in CMD.exe or in conemu64.exe but in Git Bash
16. neriousy

    marked bug: mouse escape sequences garbled after TUI exit #20458 as a duplicate of this issue on Oct 1, 2026
17. djbclark commented on Oct 2, 2026

    

    djbclark

    on Oct 2, 2026

    More actions

    Carrying over details from #20458, which was closed as a duplicate of this issue.

    Environment

    • OS: macOS 27.0.1 (26A434)
    • Terminal: Ghostty 1.3.1
    • Shell: Bash
    • OpenCode: v1 (1.18.32 installed); v2.0.18 did not reproduce in the same PTY test

    A macOS trigger for the same symptom. This is tracked separately in #51600. On macOS with Bash, OpenCode v1 can be stopped by job control automatically after startup: SIGTTOU (22) in the default mode and SIGTTIN (21) in attach mode. The stop skips teardown, so mouse reporting stays enabled and the shell then shows the same 35;...M stream described here. --pure doesn't prevent it. Running the TUI with Bash monitor mode temporarily disabled does.
18. thdxr commented on Oct 11, 2026

    

    thdxr

    on Oct 11, 2026

    Member

    More actions

    Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
19. thdxr

    closed this as not plannedon Oct 11, 2026