Terminal raw mode not restored after abnormal exit — input broken, Ctrl-like behavior #30920

Activity

1. github-actions

   assigned

   simonklee

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

   

   github-actionsBot

   on Jun 5, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [Windows] Terminal left with raw ANSI escape codes after crash (PowerShell) #21277: Terminal left with raw ANSI escape codes / broken state after crash on Windows PowerShell — same root cause (terminal raw mode not cleaned up on abnormal exit), different symptom manifestation
   • Stale stdin bytes leak to shell after exit on POSIX (space on prompt, blocks ctrl+d) #17081: Stale stdin bytes and raw mode not restored after exit — covers the raw mode cleanup issue more broadly, with related issues listed there

   If your issue is distinct (e.g. specific to the Esc-twice abort path or the Ctrl-like key behavior), feel free to clarify and a maintainer will follow up.
3. simonklee

   assigned

   Hona

   on Jun 5, 2026
4. sunny198305 commented on Jun 5, 2026

   

   sunny198305

   on Jun 5, 2026 via email

   Author

   More actions

   This is likely related to #21277 and #17081. However, my report identifies a specific trigger path: pressing Esc twice during the "thinking" phase triggers an abnormal exit that bypasses the normal Interface.close() cleanup. I also located the exact SIGINT handler at line 306145 in the compiled binary which calls process.exit() without setRawMode(false). If this specific trigger path isn't covered by the existing issues, I can help test a fix. Happy to close as duplicate if the maintainers confirm the fix for #21277/#17081 also addresses the Esc-twice abort scenario.

   …

   ---- Replied Message ---- | From | ***@***.***> | | Date | 6/5/2026 17:49 | | To | ***@***.***> | | Cc | ***@***.***>, ***@***.***> | | Subject | Re: [anomalyco/opencode] Terminal raw mode not restored after abnormal exit — input broken, Ctrl-like behavior (Issue #30920) | github-actions[bot] left a comment (anomalyco/opencode#30920) This issue might be a duplicate of existing issues. Please check: #21277: Terminal left with raw ANSI escape codes / broken state after crash on Windows PowerShell — same root cause (terminal raw mode not cleaned up on abnormal exit), different symptom manifestation #17081: Stale stdin bytes and raw mode not restored after exit — covers the raw mode cleanup issue more broadly, with related issues listed there If your issue is distinct (e.g. specific to the Esc-twice abort path or the Ctrl-like key behavior), feel free to clarify and a maintainer will follow up. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>
5. github-actions commented on Aug 5, 2026

   

   github-actionsBot

   on Aug 5, 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 Aug 5, 2026