Repository navigation
[Web UI] "Auto-accept permissions" button is disabled when "New layout and design" is enabled. #31137
Closed as not planned
Description
Description
"Auto-accept permissions" button is disabled when "New layout and design" is enabled.
The button works perfectly fine in the default (classic) layout.
It appears that in the new layout, the settings page fails to associate with a specific project. As a result, the "Auto-accept permissions" button lacks the necessary project context and cannot identify which project it belongs to, causing it to malfunction.
Plugins
none
OpenCode version
1.16.0
Steps to reproduce
"Auto-accept permissions" button is disabled when "New layout and design" is enabled.
The button works perfectly fine in the default (classic) layout.
Screenshot and/or share link
Operating System
Windows 11
Terminal
Windows Terminal
Reacted by Mike Aizatsky, Hengqian Ling, kejkej31, Michael Buckner, Eduardo Soares, Lucas Soreau, Jeremy Kahn, Matheus Castello, Yousof and DavidMorenoGlov
Metadata
Metadata
Assignees
Labels
No labels
Activity
greatbody commentedon Jun 7, 2026
Same issue
mschwartz1320 commentedon Jul 29, 2026
I can take a focused fix for this if it is not already in progress. The proposed scope is to pass the active session/directory context into the settings dialog, then use the existing session/directory auto-accept API from the toggle. No new persistent global policy or permission semantics.
I would include regression coverage plus Desktop screenshots. Would that approach be welcome?
michaelbuckner commentedon Aug 6, 2026
Same issue.
wodnerpie commentedon Aug 13, 2026
same issue, no idea why, the CLI allows me to switch but not the desktop app
kazemane-sketch commentedon Aug 23, 2026
same issue
j-jacobi commentedon Aug 24, 2026
Temporary workaround: Open the Command Palette (Cmd+P) and toggle "Auto-accept permissions".
This change will not be reflected in the settings UI.
microhobby commentedon Aug 31, 2026
Same issue
linghengqian commentedon Sep 4, 2026
meetr1912 commentedon Sep 15, 2026
issue still present.
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊