Renamed and re-platformed (verified 2026-10-02)

The project, created 2025-12-03 as code-yeongyu/oh-my-opencode, is now code-yeongyu/oh-my-openagent and brands itself OmO (“Oh My OpenAgent”). The old GitHub URL redirects. The 5.x line (npm oh-my-opencode latest 5.1.10, GitHub release v5.1.10 of 2026-10-02) ships a native omo command that runs on senpi, the author’s fork of the pi agent harness, rather than only as an opencode plugin. Existing OpenCode users migrate with omo setup. Licence: Sustainable Use License 1.0 (GitHub reports it as NOASSERTION), not an OSI open-source licence. The repo has ~70k GitHub stars.

Oh My OpenCode (OmO)

“Battery-included” agent harness that began as a plugin turning opencode into a multi-agent orchestration system. Per its README it is maintained as a personal side project (sponsored; the README says it is maintained by an AI assistant called Jobdori).

What the README describes (5.x, 2026-10-02)

  • ultrawork / ulw: add the keyword to a prompt and the agent reads the codebase, plans, verifies each step on the real surface and stops when done. mass ulw turns the job into a graph of parallel agents, each on the model that fits it.
  • Kibitzer memory: memory kept as markdown files in a git repository; a small cheap model watches the main agent and nudges it before it repeats mistakes.
  • Mixed models: /login covers Claude, ChatGPT, Kimi and GLM subscriptions; every model gets its own tuned system prompt.
  • Skills loaded on demand (browser use included), batched tool calls, malformed-argument repair, live reload of config/skills/prompts.
  • Config: ~/.omo/omo.jsonc (user) and .omo/omo.jsonc (project, closest file wins).

Install

curl -fsSL https://get.omo.dev/install.sh | bash   # installs the native omo binary  
omo  
# or: bun add -g omo-ai   /  npm i -g omo-ai  

The earlier 2025 versions (Sisyphus/oracle/librarian agents, oh-my-opencode.json, npx oh-my-opencode) described in the original note are replaced by the above; agent/model assignments and a token-spend claim from the 2025 note could not be verified against the current README and were removed.

Sources