bug: exiting tui on windows has improper exit sequence handling #5070

Activity

1. rekram1-node

   assigned

   kommander

   on Dec 4, 2025
2. rekram1-node

   added

   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

   on Dec 4, 2025
3. rekram1-node

   changed the title [-]exiting tui on windows has improper exit sequence handling[/-] [+]bug: exiting tui on windows has improper exit sequence handling[/+] on Dec 4, 2025
4. github-actions commented on Dec 4, 2025

   

   github-actionsBot

   on Dec 4, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Provide means to disable Ctrl-C #2999: Provide means to disable Ctrl-C (exact same crash on Windows with improper exit sequence)
   • Panic: close of closed channel in status component cleanup #3294: Panic: close of closed channel in status component cleanup (core infrastructure issue causing exit failures)
   • Bug: opencode run and TUI exits hang on v0.15+ #3213: Bug: opencode run and TUI exits hang on v0.15+ (broader exit sequence regression in v0.15+/v1.0)
   • [Windows] interactive call breaking tui #3763: [Windows] interactive call breaking tui (Windows TUI stability issues in v1.0)
   • Phantom input on startup again. #4430: Phantom input on startup again (Windows Terminal mouse events similar to your screenshot)

   Feel free to ignore if none of these address your specific case.
5. somera commented on Dec 17, 2025

   

   somera

   on Dec 17, 2025

   More actions

   When this will be fixed?
6. blank038 commented on Dec 19, 2025

   

   blank038

   on Dec 19, 2025

   Last edited by blank038

   More actions

   The issue has been reproducible since v1.0.127, I first encountered it when upgrading from v1.0.126 to v1.0.127.
   Initially, I thought it was a software conflict on my end, but I later confirmed the problem by switching back to v1.0.126, which works normally.
   As of v1.0.169, this issue still persists.

   Supplement: The /exit command operates successfully, while employing Ctrl + C precipitates the aforementioned issue. This phenomenon was observed within a test environment consisting of PowerShell integrated with opencode v1.0.185.

   😕React with 😕1Reacted by HWOUq1xd7c
7. SamuelMiller commented on Jan 16, 2026

   

   SamuelMiller

   on Jan 16, 2026

   Last edited by SamuelMiller

   More actions

   I get the same issue on Windows 11. Opencode crashes and then the terminal starts to spit out characters as shown on the above image.
8. m-aliozkaya

   marked Opencode breaks my terminal even I close it #9094 as a duplicate of this issue on Jan 17, 2026
9. rekram1-node

   marked ctrl+c退到直接导致回到shell出现自动序列化问题且无法设置屏蔽ctrl+c #9175 as a duplicate of this issue on Jan 18, 2026
10. github-actions commented on Mar 26, 2026

    

    github-actionsBot

    on Mar 26, 2026 – with GitHub Actions

    Contributor

    More actions

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

    closed this as completedon Mar 26, 2026