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
{{ message }}
Repository navigation
Esc key doesn't interrupt AI generation in the Opencode VS Code extension #4354
When using the Opencode extension in VS Code, pressing the Esc key does not stop the AI generation process.
Expected behavior:
Pressing Esc should interrupt/stop the ongoing AI response generation.
Actual behavior:
The Esc key has no effect - the AI continues generating the response and cannot be interrupted.
It often doesn’t stop with ESC in the JetBrains Rider console either.
I don't use subagents, only have Plan/Build. There is an animation (progress bar?), which can't be stopped either. I can type "STOP", but it goes to a queue.
We made it so that if a subagent needs permission the tui will automatically navigate to the subagent session so you can see what is happening in scope
We made it so that if a subagent needs permission the tui will automatically navigate to the subagent session so you can see what is happening in scope
Does the auto-navigation work currently? I'm not seeing the session switch automatically. Does this mean the fix for the permission modals is still in progress, or are these separate issues?
@mossbergmaverick yeah that should work, it switches to the child session automatically that needs permission
Got it, but why doesn't it switch back to the parent session after execution? Does it mean I have to do it manually every time? This is quite inconvenient—it kind of defeats the whole purpose of working with a subagent.
Activity
mossbergmaverick commentedon Nov 15, 2025
I double-checked again: this problem is not limited to the VSCode extension and is related to the permission dialog not being displayed. If I remove
then ESC works every time, both during agent generation and when the sub-agent executes a task.
rekram1-node commentedon Nov 16, 2025
@mossbergmaverick I can't replicate? You can't get permission dialogs to show up ever?
Was this specifically with a subagent?
mossbergmaverick commentedon Nov 16, 2025
I apologize for the imprecise description. Here's my specific use case:
In this scenario, the permission dialog doesn't appear and the ESC button fails to interrupt the process.
rekram1-node commentedon Nov 17, 2025
Gotcha yeah, currently the permission modals only show up for subagnets if you go to the subagnet view, this is confusing and non ideal I will fix
pawelel commentedon Nov 20, 2025
It often doesn’t stop with ESC in the JetBrains Rider console either.
I don't use subagents, only have Plan/Build. There is an animation (progress bar?), which can't be stopped either. I can type "STOP", but it goes to a queue.
rekram1-node commentedon Nov 21, 2025
We made it so that if a subagent needs permission the tui will automatically navigate to the subagent session so you can see what is happening in scope
pawelel commentedon Nov 28, 2025
mossbergmaverick commentedon Dec 1, 2025
Does the auto-navigation work currently? I'm not seeing the session switch automatically. Does this mean the fix for the permission modals is still in progress, or are these separate issues?
rekram1-node commentedon Dec 2, 2025
@mossbergmaverick yeah that should work, it switches to the child session automatically that needs permission
pawelel commentedon Dec 8, 2025
Using opencode in Rider’s built-in terminal causes the terminal to behave incorrectly.
Steps to reproduce:
Run opencode in the Rider terminal (I’m using only the default agents).
Observed behavior:
Pressing Esc does not interrupt the “working” animation, and my messages get queued instead.
When I press Ctrl+C, the terminal switches into some kind of mouse-input mode — every mouse move prints weird characters into the terminal.
The terminal returns to normal only after closing and reopening it inside Rider.
Additional note:
This behavior occurs only with opencode. Other tools do not trigger the issue.
mossbergmaverick commentedon Dec 31, 2025
Got it, but why doesn't it switch back to the parent session after execution? Does it mean I have to do it manually every time? This is quite inconvenient—it kind of defeats the whole purpose of working with a subagent.
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.