← Back to directory
O

oh-my-openagent

Community
Multi-agent coding harness for complex codebases, spanning OpenCode and Codex CLI
GitHub source repository ↗
★ 67.3k Stars Category · Dev Tools Very popular
52FMRS · D
Reliability
7/20
Security and permissions
9/20
Maintenance
14/20
Documentation
13/20
Setup experience
9/20

The README quotes several social-media endorsements (e.g., replacing a Cursor subscription, clearing thousands of eslint warnings) that are self-selected third-party testimonials not independently verified here. It also cites a tweet claiming Anthropic blocked OpenCode 'because of us' — this is the project's own framing of a linked third-party post, and this profile does not independently verify that claim.

Read the FMRS scoring method →

oh-my-openagent (aka omo/lazycodex) is a community-maintained coding-agent harness shipped in two editions: Ultimate (for OpenCode, with 11 agents, 54+ lifecycle hooks, built-in MCPs, and Team Mode) and Light (for Codex CLI, with portable components like rules injection, comment checking, git-bash, LSP, ultrawork, and ulw-loop). It orchestrates multiple LLM providers (Claude, GPT, Kimi, GLM, Gemini, and others), bundles MCP servers for web search (Exa), docs (Context7), and GitHub code search (grep_app), and adds LSP and ast-grep tooling so agents can autonomously drive coding tasks to completion.

Tools

lsp_rename
Renames a symbol across the codebase via Language Server Protocol integration.
lsp_goto_definition
Jumps to a symbol's definition via LSP.
lsp_find_references
Finds all references to a symbol via LSP.
lsp_diagnostics
Retrieves LSP diagnostics (errors/warnings) for the codebase.
team_create
Creates a new Team Mode session with a lead agent and parallel members.
team_send_message
Sends a message between the team lead and team member agents.
team_task_create
Creates a task item for a team member to work on.
team_status
Reports the current status of team members and their tasks.

Setup

Ultimate edition (OpenCode): run bunx oh-my-openagent install; the TUI walks through subscription detection, model selection across the 11 agents, and provider auth, and registers the plugin in opencode.json. Light edition (Codex CLI): run npx lazycodex-ai install (non-interactive recommended: --no-tui --codex-autonomous); the installer writes to ~/.codex/plugins/cache/sisyphuslabs/omo/, a local Codex marketplace cache, marketplace/plugin/agent blocks in ~/.codex/config.toml, and component CLIs in ~/.local/bin. Use --platform=both to install both editions. Do not run bunx omo/npx omo — that bin alias collides with an unrelated third-party npm package of the same name.

claude_desktop_config.json
{"plugin": ["oh-my-openagent"]}

Fit and risk

Best for

  • Developers already on OpenCode or Codex CLI who want multi-model agent orchestration
  • Teams wanting automated hierarchical AGENTS.md generation and project rule injection
  • Users comfortable granting an agent broad autonomous edit/execution permissions for speed

Not for

  • Users who want a small, single-purpose MCP tool server with a minimal attack surface
  • Workflows requiring strict human review of every file edit or command before it runs
  • Projects requiring vendor-official support rather than a community-maintained plugin
  • Users not running OpenCode or Codex CLI as their agent host

Required permissions

  • Read/write access to the project codebase (for autonomous code edits)
  • Ability to execute shell/terminal commands (tmux integration, git-bash component)
  • Network access for bundled MCPs (Exa web search, Context7 docs, grep_app GitHub search)
  • API keys/subscription auth for multiple LLM providers (Anthropic, OpenAI, Kimi, GLM, Gemini, Copilot, etc.)
  • For the Codex Light edition, write access to `~/.codex/` config, plugin cache directories, and `~/.local/bin`

Risks and side effects

  • Agents have broad autonomous file-edit and command-execution permissions; `ultrawork` mode does not stop until it decides the task is complete, risking large unreviewed changes
  • The Codex Light installer offers a `--codex-autonomous` full-permissions mode that removes command-confirmation gating
  • Anonymous telemetry (hashed machine ID, at most once per day) is enabled by default and must be manually opted out
  • Third-party community project; the README notes an in-progress multi-harness refactor, so behavior may shift between versions
  • Requires credentials/subscriptions from multiple third-party model providers, expanding the credential surface
  • The `omo` bin alias collides with an unrelated third-party npm package, risking accidental installation of the wrong tool

Troubleshooting

  1. Run `bunx oh-my-opencode doctor` (or oh-my-openagent doctor) to verify plugin registration, config, models, and environment
  2. Confirm `opencode.json`'s plugin array includes `oh-my-openagent` (or the legacy `oh-my-opencode` entry)
  3. Check config resolution: project-level `.opencode/oh-my-openagent.json[c]` files are walked up to `$HOME`, with the closest one winning
  4. For the Codex Light edition, inspect `~/.codex/config.toml` for the marketplace/plugin/agent blocks and check `~/.codex/plugins/cache/sisyphuslabs/omo/`
  5. Avoid `bunx omo`/`npx omo`; use `oh-my-openagent`, `oh-my-opencode`, or `lazycodex-ai` instead
  6. If Team Mode's team_* tools don't appear, confirm `team_mode.enabled` is set to true in the config and restart opencode

Use cases

Autonomous multi-agent coding (Sisyphus, Hephaestus, Prometheus, etc.) on complex codebases in OpenCode
One-word `ultrawork`/`ulw` invocation that plans, delegates, and drives a task to completion
Team Mode for adversarial plan review (hyperplan) or parallel security research with multiple agents
Lightweight portable components (rules, LSP, ast-grep, comment checking) inside Codex CLI without full agent orchestration

Supported clients

OpenCodeFull support
Codex CLIFull support