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
When I clicked "Allow once", I couldn't click it. When I clicked "Allow always", it kept repeatedly jumping to "Always allow", and when I clicked "Reject", I couldn't submit the content in "Tell Opencode what to do differently", causing the session to get stuck here. Moreover, even after I directly closed the VSCode Opencode plugin, it still showed in the "Operation Env" and I couldn't continue the operation.
Plugins
vscode
OpenCode version
1.14.48
Steps to reproduce
The current situation I'm facing is as follows: When opencode attempts to read or write the .env file again and requires permissions, this problem may occur.
Screenshot and/or share link
No response
Operating System
windows 11
Terminal
windows terminal
Reacted by Artur Gomes, Patrick Vickery, wannoradzahari, Tomasz M. Witczak, Levein.Zhang, jason, よすみ, samuel-pullely, Paweł Cyman, beefeater7 and 1 more
Same symptoms — permission dialog options (Allow once, Allow always, Reject) cannot be selected using either keyboard or mouse. Also affects Esc to cancel/stop actions. Not limited to Windows.
Confirming this on v1.16.0 (Linux x86_64, VS Code integrated terminal, xterm-256color).
Symptoms:
"Allow once" and "Reject" are unresponsive — clicking or pressing Enter does nothing
"Allow always" does register — it shows the "Always allow" confirmation dialog listing the matched patterns, and clicking Confirm succeeds
But after confirming "Always allow", it loops back to the same permission dialog for the same command, and the buttons are unresponsive again
Ctrl+P command menu opens, but selecting "Exit the app" from it also does nothing
Only fix is to kill the process externally
Happens intermittently — sometimes the dialog works fine, other times it freezes on first appearance
Environment:
OpenCode v1.16.0
Linux (container, kernel 6.8.0, x86_64)
Terminal: VS Code integrated terminal (xterm-256color)
Shell: zsh
Additional observations:
Non-deterministic: starting a new session in the same directory doesn't always reproduce it, but once a session is stuck it's non-recoverable
The "Always allow" confirm loop suggests the permission approval isn't being persisted or the command is being re-evaluated before the approval takes effect
I think I may have figured out the cause. When I switch to web mode, a rather odd log like this pops up. I suspect this issue is identical to the one in cmd mode — it feels like a certain index has gone missing.
我猜我可能找到了原因,当我切换到web模式下,会出现这样一个神奇的log。我怀疑这个问题和cmd模式下的这个问题是一样的,就像是丢失了某个索引。
Activity
github-actions commentedon May 14, 2026
This issue might be a duplicate of existing issues. Please check:
1122414 commentedon May 14, 2026
opencode.mp4
arturgoms commentedon May 18, 2026
That is also happening to me on 1.15.3
MichalCz commentedon May 20, 2026
This is still happening to me as well. Any chances to fix this and a temporary workaround?
maojianh commentedon May 28, 2026
The issue persists and has not been resolved.
v1.15.11
Rajeshwaran-R commentedon May 29, 2026
facing same in v1.15.12
Rajeshwaran-R commentedon May 29, 2026
I uninstall and reinstalled opencode via curl. The same version works for me on same working directory with same model and prompt.
DerekCorniello commentedon Jun 1, 2026
Happening to me today on v1.15.13.
jasonfirkus commentedon Jun 1, 2026
Happening to me right now
arimotearipo commentedon Jun 2, 2026
Is there a fix or a workaround for this? This has made opencode practically unusable for me.
ztobs commentedon Jun 5, 2026
Also affected on Linux:
Operating System: Ubuntu 26.04 LTS (Resolute Raccoon)
Kernel: Linux 7.0.0-22-generic x86_64
Desktop: GNOME (Wayland)
Terminal: GNOME Terminal (xterm-256color)
Shell: zsh
Node: v23.1.0
OpenCode version: v1.15.12 through v1.16.0
Same symptoms — permission dialog options (
Allow once,Allow always,Reject) cannot be selected using either keyboard or mouse. Also affectsEscto cancel/stop actions. Not limited to Windows.samuel-pullely commentedon Jun 5, 2026
Confirming this on v1.16.0 (Linux x86_64, VS Code integrated terminal, xterm-256color).
Symptoms:
Environment:
Additional observations:
samuel-pullely commentedon Jun 5, 2026
@Hona gentle ping — this is still affecting multiple users on v1.16.0. Any progress on a fix?
dhlang001 commentedon Jun 6, 2026
no...Still happing...v1.16.2
DerekCorniello commentedon Jun 7, 2026
I haven't been able to reproduce in a while, I am on v1.16.2
nfedyashev commentedon Jun 12, 2026
Starting to experience this only after 1.17.4 upgrade, it was completely unusable for me.
* UPDATE
After I did downgrade
opencode upgrade 1.16.2it works fine againdhlang001 commentedon Jun 13, 2026
I think I may have figured out the cause. When I switch to web mode, a rather odd log like this pops up. I suspect this issue is identical to the one in cmd mode — it feels like a certain index has gone missing.
我猜我可能找到了原因,当我切换到web模式下,会出现这样一个神奇的log。我怀疑这个问题和cmd模式下的这个问题是一样的,就像是丢失了某个索引。
github-actions commentedon Aug 13, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.