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
In plan mode, entering a prompt can cause opencode to attempt writing or applying changes to workspace files. When edit permission is denied, the request fails instead of remaining read-only or asking for permission appropriately.
Install/channel: Unavailable: executable output did not identify the install channel
Active plugins: None configured in the inspected project and user configs; the previously listed /Users/billyhawkes/Projects/211-search/tmp/luna-fix.ts file was not present when inspected
Reproduction
Start opencode in plan mode.
Enter a prompt that causes the session to produce or apply a workspace change.
Observe the resulting permission error.
Expected Behavior
Plan mode should not write to workspace files. It should either keep the proposed changes in the plan/session view or explicitly request edit permission before attempting a file operation.
Actual Behavior
The prompt causes opencode to attempt to write to files. The operation fails with:
# Patch failed
Permission denied: edit
I can’t apply the session view because workspace edit permission was denied twice before any files were changed.
Additional Context
The failure was observed while entering a prompt in plan mode. No files were changed because edit permission was denied twice. Reproduction frequency, the exact prompt, and whether the issue occurs in every workspace are not yet confirmed.
plan mode takes actions #33526: Plan mode takes actions — plan mode executing state-modifying operations instead of staying read-only
If your issue is specifically about the permission-denied error message behavior (rather than the enforcement gap itself), it may still be worth keeping open, but please check the above issues first.
Activity
github-actions commentedon Jul 16, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about the permission-denied error message behavior (rather than the enforcement gap itself), it may still be worth keeping open, but please check the above issues first.
github-actions commentedon Sep 15, 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.