OmO

tom@tomrochette.com (Tom Rochette) — Tue, 13 Oct 2026 00:00:00 +0000

OmO is the working name of code-yeongyu/oh-my-openagent, a source-available CLI coding agent at roughly 70,000 stars that runs on senpi (its fork of the Pi harness) and bundles a memory system, CodeMode, multi-model ultracode, Anthropic subscription support, and a workflow-DAG side pane.

It is the scale-versus-trust test case of the Pi-derivative family: twice the stars of any other member of that family, with a mascot listed as the maintainer, a sponsor in the README, and a custom license that assigns different terms to different portions of the code.

What it is
#

A terminal agent distributed through an install script (get.omo.dev), built on OmO 5.0’s announced Pi base: the senpi fork contributes the harness core, and OmO layers a memory system, CodeMode execution, MCP support, multi-model ultracode (running several models on one task), and Anthropic subscription billing. Workflow visualization comes through omo-herdr-dag, a companion project that renders live OmO workflow DAGs in a Herdr side pane. The README is sponsor-supported (OpenGateway, an OpenAI-compatible gateway, is the backer) and states the project is maintained by Jobdori, an AI assistant persona.

Status
#

Massively starred and fast-moving: 69,986 stars, 5,750 forks, and 1,272 open issues as of 2026-10-13, pushed the day of this check, with release v5.1.32 published 2026-10-13. The governance record is the caution: the repository moved from an organization that now 404s, the license is a custom per-portion document GitHub reports as NOASSERTION rather than any standard license, and the README names an AI assistant as the maintainer beside its sponsor, so the usual signals a 70,000-star project carries are absent or inverted. Independent discussion exists but is thin for the scale: two 4-point Hacker News threads (May and September 2026) and no sustained third-party coverage found.

Strengths
#

Capability breadth for a CLI agent: memory, CodeMode, MCP, multi-model execution, and subscription billing in one install script.
The Pi lineage gives it a working harness core rather than a from-scratch framework, and Pi upstream ideas flow through the fork.
Shipping velocity is genuine: a release published the day of verification and continuous pushes.
The Herdr DAG side pane gives long-running work a visible workflow graph, which most terminal harnesses lack entirely.
The size of the community is itself information: at this star count, breakage gets reported fast.

Cautions
#

The license is the headline risk: a custom per-portion document with no standard identifier, so redistribution and internal-use rights must be read term by term before adoption.
Provenance is murky: the original organization 404s, the maintainer of record is an AI persona, and a sponsor’s gateway product sits in the README funnel.
The misspelled third-party reference inside the license (“oh-my-opencode”) suggests the text was adapted rather than written for this project, which is the kind of detail a lawyer will care about.
1,272 open issues against a side-project maintenance story argues the issue tracker is a wish wall, not a backlog.
Thin independent coverage for the star count keeps the stars-ahead-of-discussion flag this section applies to Cabinet-class records.

Pricing
#

The code is free to install and the README advertises no paid plan; Anthropic subscription usage is billed by Anthropic under your own login, and the README’s sponsor sells a separate gateway product. The license file, not a pricing page, is what actually constrains use.

Compared to
#

Pi: the upstream harness OmO forks; Pi is MIT, smaller, and explicit about its design, OmO is bigger and bundled.
Oh My Pi: the other large Pi derivative at about half OmO’s scale, with a cleaner licensing story; the like-for-like alternative inside the family.
OpenCode: the vendor-neutral terminal harness with standard licensing; the safer default at any budget.

Bottom line
#

Recommended for tinkerers who want the most bundled terminal agent available and will read the custom license and pin the version they audit. Not for commercial use without legal review, for teams needing standard licensing and identifiable maintainers, or for anyone who wants upstream Pi rather than a fork.

Changes
#

2026-10-13 - Created.

References
#

https://github.com/code-yeongyu/oh-my-openagent - repository, custom license file, stars, fork count, push activity, and the OmO 5.0 Pi-base announcement as of 2026-10-13
https://github.com/code-yeongyu/oh-my-openagent/blob/dev/README.md - the README: memory, CodeMode, Anthropic subscriptions, ultracode, sponsors, and the maintainer persona statement
https://github.com/jc01rho/omo-herdr-dag - the companion workflow-DAG side-pane project
https://get.omo.dev/install.sh - the install endpoint behind the curl one-liner
https://news.ycombinator.com/ - Algolia search returned two 4-point threads (May and September 2026) as the recorded thin independent footprint

pi-fork on tomrochette.com

OmO

What it is
#

Status
#

Strengths
#

Cautions
#

Pricing
#

Compared to
#

Bottom line
#

Changes
#

See also
#

References
#

pi-fork on tomrochette.com

OmO

What it is #

Status #

Strengths #

Cautions #

Pricing #

Compared to #

Bottom line #

Changes #

See also #

References #

What it is
#

Status
#

Strengths
#

Cautions
#

Pricing
#

Compared to
#

Bottom line
#

Changes
#

See also
#

References
#