This document provides a high-level overview of the installation process for oh-my-openagent (published as oh-my-opencode), including CLI installation, platform-specific binary selection, and initial model configuration. The system is designed as a multi-model agent orchestration harness for OpenCode, supporting a wide range of providers including Anthropic, OpenAI, Google Gemini, GitHub Copilot, and specialized providers like OpenCode Go or Vercel AI Gateway docs/guide/installation.md62-103
For information about the interactive TUI and CLI commands, see CLI Installation. For provider-specific authentication configuration, see Provider Authentication. For detailed troubleshooting of installation issues, see Troubleshooting Installation.
oh-my-openagent ships in two distinct editions to accommodate different user environments and feature requirements docs/guide/installation.md3-8
| Edition | Target Platform | Core Features |
|---|---|---|
| Ultimate | OpenCode | Full orchestration, 11 agents, 54+ hooks, Team Mode, ulw-loop, hashline edits. |
| Light | OpenAI Codex CLI | Portable components: rules, lsp, ultrawork, telemetry. No agent orchestration. |
Sources: docs/guide/installation.md3-15 docs/guide/overview.md99-105
The recommended way to install and configure the system is through the interactive installer, which handles both plugin registration and configuration generation docs/guide/installation.md12-14
The install command detects whether it should run in TUI mode (for interactive terminals) or non-interactive mode (via --no-tui) docs/reference/cli.md59 Note that oh-my-openagent and oh-my-opencode are dual-published during the transition period docs/reference/cli.md3-8
Sources: docs/guide/installation.md10-15 docs/reference/cli.md45-72 packages/omo-codex/scripts/install-local.mjs67-84
The installation process generates a configuration file that maps agents to specific models based on your available subscriptions and providers docs/reference/configuration.md69-70
The installer maps user subscriptions to provider availability. This tracks which native providers (Anthropic, OpenAI, Google) or integrated gateways (Copilot, OpenCode Zen, OpenCode Go) are accessible docs/reference/cli.md60-69
Subscription to Configuration Flow
Sources: docs/reference/cli.md45-72 docs/reference/configuration.md71-143 docs/guide/installation.md100-118
The system assigns each agent a model that matches its working style. Sisyphus (orchestrator) prefers Claude/Kimi/GLM, while Hephaestus (deep specialist) requires GPT-5.5 docs/guide/agent-model-matching.md13-37
| Provider Flag | Agent Impact | Primary Model Recommendation |
|---|---|---|
--claude=max20 | Sisyphus Orchestration | anthropic/claude-opus-4-7 docs/reference/features.md13 |
--openai=yes | Hephaestus / Oracle | openai/gpt-5.5 docs/reference/features.md14-15 |
--opencode-go | Sisyphus / Atlas | kimi-k2.6, glm-5 docs/reference/features.md13-31 |
--gemini=yes | Visual Engineering | google/gemini-3.1-pro docs/reference/configuration.md112-116 |
Sources: docs/guide/agent-model-matching.md7-41 docs/reference/configuration.md79-124 docs/reference/features.md11-32
Configuration files are discovered by walking from the working directory up to $HOME. User-level config is typically stored in ~/.config/opencode/ docs/reference/configuration.md44-55
Configuration Resolution Diagram
| Path Candidate | Platform | Priority |
|---|---|---|
.opencode/oh-my-openagent.jsonc | All | High (Project-specific) docs/reference/configuration.md48 |
~/.config/opencode/oh-my-openagent.jsonc | macOS/Linux | Medium (User-global) docs/reference/configuration.md53 |
%APPDATA%\opencode\oh-my-openagent.jsonc | Windows | Medium (User-global) docs/reference/configuration.md54 |
Sources: docs/reference/configuration.md44-59 docs/guide/installation.md32
After installation, verify the setup using the built-in diagnostic tools.
omo doctor to verify platform binary resolution, OpenCode version compatibility, and effective model resolution docs/reference/cli.md118-141refresh-model-capabilities to update the cached model metadata from models.dev docs/reference/cli.md38mcp oauth commands docs/reference/cli.md41Sources: docs/reference/cli.md30-41 packages/omo-codex/plugin/scripts/auto-update.mjs27-67
install command, TUI modes, and automated setup.Refresh this wiki
This wiki was recently refreshed. Please wait 1 day to refresh again.