sync-omo-config

OpenCode plugin that syncs omo configuration from .well-known/opencode endpoints to local oh-my-openagent.json.

What it does

When OpenCode starts, this plugin:

1. Reads auth.json to find wellknown authentication entries
2. Fetches .well-known/opencode from each server
3. Extracts the omo field from responses
4. Merges and writes to oh-my-openagent.json

This enables centralized distribution of oh-my-openagent configurations via your enterprise well-known server.

Installation

# Using bun
bun add sync-omo-config

# Using npm
npm install sync-omo-config

Configuration

Add to your opencode.json:

{
  "plugin": ["sync-omo-config"]
}

Server Setup

Your .well-known/opencode endpoint should return:

{
  "config": {
    // OpenCode config (validated by schema)
  },
  "omo": {
    // oh-my-openagent config (synced by this plugin)
    "agents": {
      "oracle": {
        "model": "anthropic/claude-sonnet-4-20250514"
      }
    },
    "categories": {
      "quick": {
        "model": "openai/gpt-4o-mini"
      }
    }
  }
}

The omo field is placed outside of config to avoid OpenCode's strict schema validation.

File Locations

| Platform | auth.json | oh-my-openagent.json | | -------- | -------------------------------------------------- | ------------------------------------------------------------------------------------ | | macOS | ~/Library/Application Support/opencode/auth.json | ~/.config/opencode/oh-my-openagent.json | | Linux | ~/.local/share/opencode/auth.json | ~/.config/opencode/oh-my-openagent.json | | Windows | %APPDATA%/opencode/auth.json | ~/.config/opencode/oh-my-openagent.json or %APPDATA%/opencode/oh-my-openagent.json |

Merge Behavior

• Server config is deep merged with existing local config
• Server values override local values for the same keys
• Multiple wellknown servers are processed in order (later overrides earlier)

Requirements

• OpenCode 1.0+
• Bun runtime
• Wellknown authentication configured (opencode auth add --wellknown <url>)

License

MIT