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
Notification permission is not requested with New layout enabled #37120
On top of the OP. I noticed if focus out of the browser app is lost (and even if you then go back to focus) the permission ask is never exposed through the parent/origin session, therefore as a user it's near impossible to know if a subagent is awaiting for permission ask response without actively clicking into every subagent.
I'm finding if you never lose focus of the tab or the browser page the permission ask does properly show.
This also affects the web version, not only OpenCode Desktop.
Environment:
OpenCode web UI
OpenCode backend/CLI 2.0.11, installed through npm
Windows 11
Permission sounds enabled
Other sounds, including completion and error sounds, work correctly
When a permission request appears in the web UI, no permission sound is played. The permission prompt itself renders correctly.
Looking at the v2.0.11 source, packages/app/src/shell/notifications/notification.tsx handles completion and error sounds but does not subscribe to permission.asked. The only app-side permission.asked subscription I found is for auto-approval. In contrast, the terminal TUI correctly handles this event in packages/tui/src/feature-plugins/system/notifications.ts.
This suggests the shared app/web notification path is missing permission-sound handling, rather than this being specific to the desktop shell.
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
imarshallwidjaja commentedon Jul 16, 2026
I experience the same issue.
On top of the OP. I noticed if focus out of the browser app is lost (and even if you then go back to focus) the permission ask is never exposed through the parent/origin session, therefore as a user it's near impossible to know if a subagent is awaiting for permission ask response without actively clicking into every subagent.
I'm finding if you never lose focus of the tab or the browser page the permission ask does properly show.
pdjohntony commentedon Aug 7, 2026
I also have had this issue for weeks and its been really frustrating.
AndreiShenets commentedon Sep 20, 2026
This also affects the web version, not only OpenCode Desktop.
Environment:
2.0.11, installed through npmWhen a permission request appears in the web UI, no permission sound is played. The permission prompt itself renders correctly.
Looking at the
v2.0.11source,packages/app/src/shell/notifications/notification.tsxhandles completion and error sounds but does not subscribe topermission.asked. The only app-sidepermission.askedsubscription I found is for auto-approval. In contrast, the terminal TUI correctly handles this event inpackages/tui/src/feature-plugins/system/notifications.ts.This suggests the shared app/web notification path is missing permission-sound handling, rather than this being specific to the desktop shell.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
AndreiShenets commentedon Oct 11, 2026
@thdxr the issue is reproducible in the v2
pdjohntony commentedon Oct 11, 2026
@AndreiShenets same. I think I saw somewhere on Twitter that the desktop app is not yet using the OpenCode 2 core, so thats probably why.
AndreiShenets commentedon Oct 11, 2026
It is not about the desktop or not. It is just not connected according to the agent investigation and that's for both v1 and v2