oh-my-openagent

oh-my-openagent is for the heavy terminal-agent user who has outgrown one loop. Install the Ultimate edition into OpenCode or the Light edition, lazycodex, into Codex CLI, and you get named specialists, Prometheus to plan, Hephaestus to grind, Oracle to debug, plus a team mode that runs them together. The trait that decides it is that the setup arrives tuned; you do not spend the weekend writing agent prompts.

Pick it if OpenCode or Codex is already your daily driver and your tasks span many files. Pick oh-my-claudecode if you are on Claude Code, and plain OpenCode if one agent still finishes your work.

The risk is upstream. The README states that Anthropic blocked OpenCode because of this project, which means the harness has already cost its host a provider once, and a plugin that lives inside another agent inherits every such decision. The rename from oh-my-opencode to oh-my-openagent is the visible scar; installs and docs from the old name still circulate.

Keep a second provider configured. What it does right: edits that touch symbols go through LSP tools, lsp_rename and lsp_find_references, rather than text substitution, so a rename lands everywhere the compiler thinks it should.

The design is a router with specialists. 1. Each request is classified into a category, quick for single-file changes, deep for autonomous research, ultrabrain for architecture, visual-engineering for UI, and dispatched to the agent and model bound to that category. 2. Background agents run five or more specialists in parallel with context isolation. 3. Over 54 lifecycle hooks intercept the host's loop.

No benchmark is published, and the routing table is the claim; a study of misrouted tasks would be the paper to write. The observation: model names in the routing table are the part that will be stale first.

YeonGyu Kim is an individual, and the asset is 68,659 stars of attention attached to a plugin. A plugin's business ceiling is set by its host, so the tell is the standalone beta: npm i -g omo-ai@beta installs a native omo command that no longer needs OpenCode or Codex. That is the pivot from accessory to product, and it is the right move if the crowd follows.

Pricing power: none until the standalone ships. Likely acquirer: an agent vendor hiring the author and folding the routing table into its own product. Position: watch the beta, not the plugin.

The demo is a planner handing work to a deep worker. Procurement: the install bundles MCP servers for Exa web search, Context7 documentation and Grep.app GitHub code search, so sixty terminals will be sending queries about our code to three third parties whose retention terms nobody here has read. There is no admin console, no SSO and no central log; there is no vendor, only a maintainer.

The Ultimate install requires bun, which is not on our standard image. It does not run in CI. Onboarding for an OpenCode user is an hour. Not yet; a data-flow review first.

The licence is the Sustainable Use License 1.0: I can read it, run it and modify it for myself or my company, and I cannot sell it as a service. Fair, and stated plainly. Configuration is JSONC in ~/.omo/omo.jsonc for the user and .omo/omo.jsonc in the project, discovered by walking upward, so per-repo routing lives in git.

The gap is local models: the routing table names Anthropic, OpenAI, Gemini, Kimi, GLM and Copilot, and nothing on my own box. Forkable in the personal sense, not the commercial one. Useful, with a fence around it.