Repository navigation
[FEATURE]: Add a /permissions command to set specific permissions for the agent #40909
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Instead of it being ask or auto-approve for all tools, I would like a settings section accessed from slash command like /permissions or similar, where you are able to choose specific permissions for tools. Things like is MCP use allowed, web search, safe commands and dangerous commands are also able to be set. Plus, with things like read and write, as in is the agent auto approved to read your project files, is it allowed to read all of your files, same with write. This would help a lot if I'm deep in a session and I don't want to use confusing commands and do something I don't want too, or have to edit my opencode.json.
Reacted by Zachary Cutlip, digital-spinner and Michał Wielgosz
Activity
claell commentedon Aug 22, 2026
Strong +1 from the Desktop side. In OpenCode Desktop 1.18.21 on Windows there is currently no usable way to manage permissions from within the app:
permissionrules that otherwise live inopencode.json/opencode.jsonc, no per-tool scoping, and no runtime adjustment without editing config (Desktop ignores permission rules in ~/.config/opencode/opencode.jsonc #36416 additionally reports Desktop ignoring those config rules entirely)./permissionsplus permission modes, including an LLM-checked auto mode — [FEATURE]: "Auto mode" LLM model classifier auto-approval for permissions #37564 proposes exactly that classifier approach for opencode.A
/permissionsdialog as proposed here, surfaced in the Desktop settings UI rather than only as a slash command, would close most of that gap. Runtime toggling per session (#41909) and a persistent indicator when auto-accept is active (#38289) would complement it well.zcutlip commentedon Oct 9, 2026
This dovetails with #50600. There currently is no obvious way to audit or remove persisted permissions once granted. There are
opencode api getmanipulations but they are non-obvious and require opaque identifiers like project and permission IDs.A
/permissions(or other TUI feature) to add/audit/remove persisted permissions would be ideal.opencodejr commentedon Oct 28, 2026
Thanks for the suggestion! As I understand it, you'd like a
/permissionscommand (or a settings screen) where you can set permissions per tool and category during a session: MCP tools, web search, safe vs dangerous shell commands, and reading or writing inside the project vs anywhere else. That way you wouldn't have to choose between "ask" and "auto-accept" for everything, or editopencode.json.Right now the TUI settings only offer one choice, prompt or auto-accept. Finer-grained
allow/ask/denyrules can only be set in the config file. The maintainers will consider this.Related issues you may want to follow: