You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the model decides to for instance run something that opens with $editor or tail -f or in general enter something interactive we either have to try to escape out with multiple escapes or worse do the spam ctrl c and go back with opencode -c.
My feeling is that before it could include the "cancelled out" context. For instance the log output that was displayed on the screen during the tail session or similar.
Now if I cancel out and re-send the last message it seems that the previous message/response is totally ignored.
This issue might be a duplicate of existing issues. Please check:
Linked files are broken when using history #1637: Linked files are broken when using history - describes similar context loss issues when using Ctrl+C to cancel, where history entries become corrupted
press ESC again to interrupt does not work #888: Press ESC again to interrupt does not work - describes the exact same issue where ESC doesn't properly interrupt interactive commands, requiring Ctrl+C
Activity
github-actions commentedon Aug 30, 2025
This issue might be a duplicate of existing issues. Please check:
/compactis not interruptable #606: /compact is not interruptible - similar issue where escape sequences don't work to interrupt running commandsFeel free to ignore if none of these address your specific case.
rekram1-node commentedon Sep 13, 2025
this should be fixed in next release