← ClaudeAtlas

opencode-permissionslisted

Use this skill when configuring OpenCode's permission system — controlling which tools require approval, setting granular bash command rules, managing external directory access, configuring per-agent permissions, or understanding the allow/ask/deny permission model. Covers wildcards, pattern matching, doom loop detection, and the complete permission key reference.
Timmy6942025/opencode-builder-skill · ★ 1 · AI & Automation · score 72
Install: claude install-skill Timmy6942025/opencode-builder-skill
# OpenCode Permissions > **📚 Official Docs:** For the latest information, always refer to the official documentation: > [https://opencode.ai/docs/permissions/](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: ```json { "$schema": "https://opencode.ai/config.json", "permission": "allow" } ``` ### Set Per-Tool Permissions Override specific tools while keeping a global default: ```json { "$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 ```json { "$schema": "https://opencode.ai/config.json", "permission": { "bash": { "*": "ask", "git *": "allow", "npm *": "all