optimize-permissions

Reduce repeated opencode permission prompts by analyzing usage data from the opencode database to identify frequent checks, then applying targeted guardrails to your config. This reveals inefficiencies in bash command patterns and MCP tool usage, allowing you to relax or tighten rules.

Auditing opencode permission config involves reviewing current rules to find redundant or conflicting guardrails using last-match-wins semantics. Config-audit identifies misconfigurations by analyzing prompt frequency and denial counts, producing concrete config changes with minimal risk.

Configure opencode guardrails by scanning the opencode database to target bash command patterns and MCP tool usage. Scenario-driven recommendations help tighten or relax non-destructive read and write actions, generating actionable config updates for your global opencode.jsonc file.

Yes, you can analyze opencode database queries to surface frequent prompts and denial counts for non-destructive read/write actions. This usage-analysis targets inefficiencies across tools and provides a plan to update your global opencode.jsonc with concrete guardrail recommendations.

Opencode config may still trigger prompts due to conflicting rules caused by last-match-wins semantics. A config-audit reviews your current permission setup to identify missing guardrails and redundant checks, providing concrete recommendations to tighten or relax rules efficiently.

Opencode permission analysis works without external dependencies by inspecting the opencode database via opencode db queries. It applies guardrails internally to analyze bash command patterns, MCP tool usage, and read/write actions, producing concrete config changes and rationale directly.