code-yeongyu / oh-my-openagent

curl -fsSL https://get.omo.dev/install.sh | bash
omo

On Windows, in PowerShell: irm https://get.omo.dev/install.ps1 | iex. The script installs the native omo binary for your OS and CPU into ~/.local/bin, checks it against the release checksums, and falls back to GitHub Releases when the mirror is unreachable. Add -s -- beta (or a version such as -s -- 5.1.1) after bash to pick another channel. Windows CMD, fixing your PATH, updating and uninstalling are covered at omo.dev/docs/install.

Prefer a package manager? bun add -g omo-ai (or npm i -g omo-ai) installs the same OmO. The package is omo-ai; the unrelated omo package on npm is someone else's.

Open your project, run omo, describe the job. That's the whole setup.

In a session, /thinking <level> sets how hard the model thinks (/thinking alone opens a picker), Shift+Tab cycles through the levels, and /efforts <level> sets the reasoning effort directly on models with effort grades. To pick up earlier work, /resume (or /sessions) opens your past sessions; from the shell, omo -c continues the last one and omo -r opens the picker. /help lists everything else.

Coming from the OpenCode edition or LazyCodex? Run omo setup once. It carries your provider keys, custom providers, MCP servers, skills and model picks across. omo doctor then shows which task categories your providers can run and what the old install left behind, and omo doctor --models shows which model each category and agent runs and in what order (keep one out everywhere with exclude_models). The full walkthrough is Migrating from OpenCode.

To update, run the install line again (a package-manager install updates with omo update). rm ~/.local/bin/omo removes the binary install; bun remove -g omo-ai (or npm uninstall -g omo-ai) removes the package install.

Development Setup

# Clone the repository (with the frontend provenance submodules)
git clone --recurse-submodules https://github.com/code-yeongyu/oh-my-openagent.git
cd oh-my-openagent

# If you cloned without --recurse-submodules, initialize them now (non-fatal offline):
git submodule update --init --recursive

# Install dependencies (bun only - never use npm/yarn)
bun install

# Build the project (materializes the frontend third-party references from the submodules)
bun run build

The frontend skill's brand / taste / ui-ux references are third-party content kept ONLY as pinned git submodules under packages/shared-skills/upstreams/. The repo contains zero committed copies; the build materializes them into packages/shared-skills/skills/frontend/references/ (gitignored locally, shipped in the published package). script/agent/setup.sh runs the submodule init + materialize for you (both non-fatal, so an offline checkout still builds, just without the brand refs).