Configuration

Configuration File Locations

Oh My OpenCode looks for configuration in the following locations (in order of precedence):

1. .opencode/oh-my-opencode.json - Project-specific configuration (highest priority)
2. ~/.config/opencode/oh-my-opencode.json - User-wide configuration

Project-specific configuration takes precedence over user-wide configuration. This allows you to have different settings for different projects.

Agents Configuration

Configure which agents are enabled and their settings:

{
  "agents": {
    "planner-sisyphus": {
      "enabled": true,
      "replace_plan": true
    },
    "librarian": {
      "enabled": false
    },
    "explore": {
      "enabled": false
    },
    "oracle": {
      "enabled": false
    }
  }
}

Agent Options

Learn More About Agents →

Hooks Configuration

Disable specific built-in hooks via disabled_hooks:

{
  "disabled_hooks": ["comment-checker", "agent-usage-reminder"]
}

Available Hooks

The following hooks can be disabled:

• todo-continuation-enforcer - Ensures tasks are completed
• context-window-monitor - Monitors context window usage
• session-recovery - Automatic session recovery
• session-notification - Session event notifications
• comment-checker - Code comment validation
• grep-output-truncator - Truncates large grep outputs
• tool-output-truncator - Manages tool output sizes
• directory-agents-injector - Injects directory-specific agents
• directory-readme-injector - Adds README context
• empty-task-response-detector - Detects empty responses
• think-mode - Enables thinking mode
• anthropic-context-window-limit-recovery - Handles Anthropic limits
• rules-injector - Injects custom rules
• background-notification - Background notifications
• auto-update-checker - Checks for updates
• startup-toast - Startup notifications
• keyword-detector - Keyword detection
• agent-usage-reminder - Agent usage reminders
• non-interactive-env - Non-interactive environment handling
• interactive-bash-session - Interactive session management
• empty-message-sanitizer - Cleans empty messages
• compaction-context-injector - Context compaction
• thinking-block-validator - Validates thinking blocks
• claude-code-hooks - Claude-specific hooks
• ralph-loop - Ralph agent loop
• preemptive-compaction - Preemptive compaction

Learn More About Hooks →

MCPs Configuration

Disable specific MCPs via disabled_mcps:

{
  "disabled_mcps": ["context7", "grep_app"]
}

Available MCPs

• context7 - Fetches up-to-date official documentation for libraries (enabled by default)
• grep_app - Ultra-fast code search across millions of public GitHub repositories (enabled by default)

Learn More About MCPs →

LSP Configuration

Add and configure LSP servers:

{
  "lsp": {
    "typescript-language-server": {
      "command": ["typescript-language-server", "--stdio"],
      "extensions": [".ts", ".tsx"],
      "priority": 10
    },
    "pylsp": {
      "disabled": true
    }
  }
}

LSP Server Options

Learn More About LSP →

Experimental Features Configuration

Opt-in experimental features that may change or be removed in future versions:

{
  "experimental": {
    "preemptive_compaction_threshold": 0.85,
    "truncate_all_tool_outputs": true,
    "aggressive_truncation": true,
    "auto_resume": true,
    "dcp_for_compaction": false
  }
}

Experimental Options

Learn More About Experimental Features →

Complete Configuration Example

Here's a complete example configuration file:

{
  "agents": {
    "planner-sisyphus": {
      "enabled": true,
      "replace_plan": true
    },
    "librarian": {
      "enabled": true
    }
  },
  "disabled_hooks": ["comment-checker"],
  "disabled_mcps": [],
  "lsp": {
    "typescript-language-server": {
      "command": ["typescript-language-server", "--stdio"],
      "extensions": [".ts", ".tsx"],
      "priority": 10
    }
  },
  "experimental": {
    "preemptive_compaction_threshold": 0.85,
    "auto_resume": false
  }
}

Configuration Validation

Oh My OpenCode validates your configuration on startup. If there are any errors, they will be reported and the default configuration will be used for invalid sections.

Common Configuration Errors

• Invalid JSON syntax - Make sure your JSON is valid. Use a JSON validator if needed.
• Unknown options - Check that option names are spelled correctly.
• Invalid values - Ensure values match the expected types (boolean, number, string, array, object).