OpenCode Config

Portable personal OpenCode configuration with reusable agents, commands, skills, browser MCPs, and conservative permission defaults.

• Chrome and WebKit browser MCPs with inspection tools auto-approved.
• Browser QA, code-review finder/verifier, and code-simplifier agents.
• /code-review, /fix-quality, /cleanup-comments, /grill-me, and /tldr.
• Frontend design, interface polish, and decision-framework skills.
• A shell guard that prevents auto-approved read commands from hiding chained commands, substitutions, or redirections.
• Type checking and tests for custom plugins.

The config intentionally excludes credentials, session state, logs, local-model permission automation, organization-specific MCPs, iOS tooling, and project-specific database or Git workflows.

Requirements:

• OpenCode
• Node.js 24.15 or newer and npm
• Git
• Chrome for the Chrome MCP

git clone <repository-url> ~/Code/opencode-config
~/Code/opencode-config/install.sh

The installer creates ~/.config/opencode as a symlink to this checkout's config/ directory and runs npm ci. It refuses to overwrite an existing configuration.

Authenticate providers separately on each machine. Never copy ~/.local/share/opencode/auth.json or mcp-auth.json into this repository.

After changing configuration, agents, commands, skills, or plugins, quit and restart OpenCode.

If ~/.config/opencode already exists, compare and back it up before replacing it:

mv ~/.config/opencode ~/.config/opencode.backup
~/Code/opencode-config/install.sh

Do not move a running OpenCode session's configuration until you are ready to restart it.

npm ci
npm run check
opencode debug config
opencode debug skill

opencode debug config validates the effective configuration but may include project-local overrides when run inside another repository. Run it from this checkout for the global baseline.

Install terminal-notifier:

brew install terminal-notifier

Then add "./optional/notify.ts" to the plugin array in config/opencode.jsonc.

Add these only on machines where they are useful, then authenticate locally:

{
  "mcp": {
    "ios-simulator": {
      "type": "local",
      "command": ["npx", "-y", "ios-simulator-mcp@1.6.0"],
      "enabled": true
    },
    "sentry": {
      "type": "remote",
      "url": "https://mcp.sentry.dev/mcp",
      "enabled": true
    }
  }
}

Organization-specific MCPs should generally live in a private branch or a separate local config rather than a public repository.

Keep commands tied to one repository under that project's .opencode/ directory. Database reset/migration commands and hard-coded branch workflows do not belong in this global configuration.

Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.