Skip to content

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

Closed as not planned

Description

@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

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Apr 9, 2026
  2. github-actions commented on Apr 9, 2026

    @github-actions
    Contributor

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

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

  3. sim590 commented on Apr 18, 2026

    @sim590

    Confirming this is still present on 1.4.7.

    In my case, the agent had just run git merge origin/dev 2>&1 (which reported 4 conflicts), then ran grep -n to locate conflict markers in one of the files. After that, the TUI showed ~ Writing command... and got stuck there.

    • ESC did not work — the UI was visually responsive (I could scroll, etc.) but pressing ESC had no effect on stopping the agent
    • Had to force-kill the process to regain control
    • After restarting and telling the agent to continue, it resumed conflict resolution normally

    This matches the description: the abort signal is no longer plumbed through to shell execution, so ESC cannot interrupt.

  4. removed
    bugSomething isn't working
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  5. github-actions commented on Jul 4, 2026

    @github-actions
    Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions