opencode-permissions

OpenCode Permissions

📚 Official Docs: For the latest information, always refer to the official documentation: https://opencode.ai/docs/permissions/

Control which actions require approval to run in OpenCode.

OpenCode uses the permission config to decide whether a given action should run automatically, prompt you, or be blocked. Permissions control what tools can do during a session.

---

Actions

Each permission rule resolves to one of three actions:

Action	Behavior
"allow"	Run without approval
"ask"	Prompt for approval before running
"deny"	Block the action entirely

---

Configuration

Set All Permissions at Once

You can set a global default for all permissions:

{
  "$schema": "https://opencode.ai/config.json",
  "permission": "allow"
}

Set Per-Tool Permissions

Override specific tools while keeping a global default:

{
  "$schema": "https://opencode.ai/config.json",
  "permission": {
    "*": "ask",
    "bash": "allow",
    "edit": "deny"
  }
}

---

Granular Rules (Object Syntax)

For most permissions, you can use an object to apply different actions based on the tool input. Rules are evaluated by pattern match, with the last matching rule winning.

Basic Pattern

{
  "$schema": "https://opencode.ai/config.json",
  "permission": {
    "bash": {
      "*": "ask",
      "git *": "allow",
      "npm *": "allow",
      "rm *": "deny",
      "grep *": "allow"
    },
    "edit": {
      "*": "deny",
      "packages/web/src/content/docs/*.mdx": "allow"
    }
  }
}

In this example:

• git status → last matching rule is "git *": "allow" → allowed
• rm -rf / → last matching rule is "rm *": "deny" → denied
• npm install → last matching rule is "npm *": "allow" → allowed
• Edit to .mdx files → allowed; edit to other files → denied

Wildcards

Permission patterns use simple wildcard matching: