Oh My OpenAgent (OmO)

OmO is delivered in three editions. The OpenCode and Codex editions load as plugins into a host you already run; the Codex edition carries a subset of the components and has no team_* tool family, only a script-and-skill-driven teammode component. OmO Native is a standalone omo binary that bundles a pinned engine, senpi, described in the README as a fork of pi. The README now leads with the Native edition and describes the OpenCode edition as the one to migrate from; the OpenCode plugin remains documented as a separate edition.

Orchestration is a supervisor arrangement. The main agent runs on the session model, plans, and calls task to hand work to a category worker in a fresh session or to one of four read-only curated agents. Keyword prompts such as ultrawork or ulw inject mode instructions, and mass ulw turns a job into a graph of agents run in waves. The README's counts of agents per job (hundreds) are its own claim. Team Mode adds a lead-and-members structure with a shared mailbox and task list, and is off by default.

State is file-based: settings in ~/.omo/omo.jsonc with project overrides, plan files under .omo/plans/, team specs under .omo/teams/, and boulder and goal state for continuing work across sessions. Memory is markdown in a git repository read by the Kibitzer sidecar, which cannot write memory or files.

Planning is the main approval point: /ulw-plan interviews the user and produces a plan that the user then executes with /ulw-execute. /stop-continuation stops todo continuation, the active goal and boulder state, /goal can pause or resume a goal, and /handoff writes a summary for a new session. Permissions and tool allowlists are configurable, and the docs say AGENTS.md is instruction context, not an enforcement boundary. The Codex Light installer offers an autonomous mode that sets approval_policy = "never" and sandbox_mode = "danger-full-access", which removes approval prompts if chosen.

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

# macOS, Linux, WSL
curl -fsSL https://get.omo.dev/install.sh | bash
omo --version

# From an OpenCode install: carry over keys, MCP servers, skills and model picks
omo setup
omo doctor

# Package-manager alternative (the package is omo-ai, not omo)
bun add -g omo-ai

# OpenCode plugin edition or Codex plugin edition
bunx oh-my-openagent install
npx lazycodex-ai install

# In a project, run omo and type a prompt with a keyword or a plan command
omo
#   ultrawork <your task>
#   /ulw-plan   then   /ulw-execute

• The npm package for OmO Native is omo-ai; the plain omo package on npm is unrelated.
• oh-my-openagent and oh-my-opencode releases up to 4.19.4 install their own global omo command, which shadows OmO Native until the installer removes it.
• The bun and npm installs need Node 24 or newer; the curl installer needs no Node and refuses to run as root or Administrator.
• ulw mode is triggered per message; a follow-up without the keyword can fall back to default behaviour (tracked as a known issue).
• Team Mode is off by default and needs team_mode.enabled: true plus a restart.
• The Codex Light installer offers an autonomous mode with no approvals and full-access sandbox.
• Telemetry is on by default and can be turned off.

No. GitHub reports no license, and the LICENSE.md file contains the Sustainable Use License 1.0. It allows use and modification for internal business purposes or non-commercial or personal use, and distribution only free of charge for non-commercial purposes. It is source-available, not OSI open source.

Yes, as a client. The OpenCode edition injects built-in servers (websearch, context7, grep_app, lsp), loads .mcp.json files and starts skill-embedded servers, and OmO Native keeps servers in ~/.omo/agent/mcp.json. No MCP server of its own is documented.

OpenCode through the Ultimate edition and Codex through the Light edition, per the installation guide. OmO Native is a standalone command on a bundled pi-fork engine and needs no host.

Yes. A main agent delegates to category workers and read-only agents, background agents run in parallel, and an experimental Team Mode adds a lead, up to 8 members, a mailbox and shared task list. Team Mode is off by default.

oh-my-opencode. The features reference has a rename-compatibility section saying the published package and binary remain oh-my-opencode, with legacy plugin entries still loading with a warning.