opencode-configure

OpenCode Configuration

Navigation hub for OpenCode configuration tasks.

Information Architecture

• Quick Start — working provider + AGENTS.md in under 2 minutes
• When to Use / Scope — what this skill covers
• Mindset — mental model before diving into config fields
• Workflow — step-by-step approach
• Configuration Examples — copy-paste provider and AGENTS.md templates
• Gotchas & Production Caveats — field quirks and safety constraints
• Anti-Patterns — common mistakes with WHY/BAD/GOOD

---

Quick Start

Add a provider — create/edit opencode.json in your project root:

{
  "providers": [
    {
      "id": "anthropic",
      "baseEnv": "ANTHROPIC_API_KEY",
      "models": [
        { "id": "claude-sonnet-4-5", "default": true }
      ]
    }
  ]
}

Add project instructions — create AGENTS.md in project root:

## Workflow Rules
- Run `npm test` after every code change.
- Never modify `package.json` without user confirmation.

Validate config:

jq . opencode.json && opencode run "test"

---

When to Use

• Adding or updating providers and model preferences.
• Editing permissions for tools, shell commands, or file access.
• Updating formatter or instruction configuration in opencode.json.
• Creating or refining AGENTS.md instructions.
• Diagnosing configuration precedence or behavior mismatches.

When Not to Use

• General coding implementation tasks.
• Plugin/tool development outside standard config fields.
• Agent personality design unrelated to config structure.

Mindset

• Prefer explicit, minimal configuration changes over broad rewrites.
• Treat permissions and secrets as security-critical defaults.
• Validate behavior immediately after each meaningful config edit.

Scope

File	Purpose
opencode.json	Main OpenCode runtime configuration
AGENTS.md	Project-level behavior and workflow rules
.env/shell env	Provider keys and environment-backed configuration
references/*.md	Deep configuration guidance