Shell/session interrupt regression in 1.4.2 can leave TUI stuck and shutdown timing out

[samiralibabic]

Description

Description

On 1.4.2, interrupting a long-running shell/session action can leave OpenCode stuck instead of returning cleanly to idle.

Observed behavior:

• Esc twice does not reliably interrupt
• the session can remain busy/stuck
• TUI shutdown can end with:
  worker shutdown failed
• downgrading to 1.3.17 fixes it

This appears to be a regression in shell/session cancellation behavior introduced after 1.3.17.

Plugins

Custom plugin present in my normal setup (rexd-target), but the same setup works on 1.3.17 and breaks on 1.4.2.

OpenCode version

1.4.2

Steps to reproduce

1. Start a long-running shell/session action in TUI
2. Press Esc twice to interrupt
3. Observe that interruption is unreliable and the session may remain stuck
4. Exit TUI
5. Observe possible shutdown timeout / worker shutdown failure

Screenshot and/or share link

No response

Operating System

macOS

Terminal

Safari for web repro; TUI repro in normal terminal usage

[github-actions]

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

• GUI hangs during shell/tool execution (requires manual interrupt to continue) #21705: GUI hangs during shell/tool execution requiring manual interrupt to continue (similar hang/stuck behavior)
• Interrupted tool calls permanently corrupt session history (orphaned tool_use without tool_result) #21326: Interrupted tool calls permanently corrupt session history, causing silent TUI hang with no feedback

If your issue is distinct from the above, please add clarifying details to differentiate.