code-yeongyu/oh-my-openagent

Choose this fork if you want an opinionated, workflow-heavy agent runtime with browser and tmux subagent support. Choose upstream if you value freshness, lower merge risk, and the broadest support for recent fixes and features.

Choose upstream unless you specifically want a frozen, brandable base to fork further. For adopters, this fork offers little functional evidence beyond packaging/positioning, while carrying a large maintenance and compatibility risk from being 3,291 commits behind.

Treat this as an outdated baseline, not a meaningfully extended fork. Choose it only if you specifically need the older snapshot; otherwise upstream is the better adoption target.

Choose upstream unless you specifically want this fork's branding or ownership. The fork does not show feature additions, and it is far enough behind that adopters should assume they will miss recent upstream improvements.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

Prefer this fork only if you specifically want its curated CLI/subagent direction and are comfortable owning a stale, highly divergent codebase. If you want current fixes, broad compatibility, or a lower-risk adoption path, upstream is the safer choice.

Choose this fork if your priority is running the agent harness with smaller models and you value the added refactor/config/skill workflow changes. Choose upstream if you want the latest fixes, maximum plugin/model compatibility, and an actively maintained baseline.

Choose this fork only if you specifically want its branded, opinionated direction and are prepared to maintain it yourself. For most adopters, upstream is the safer choice because this fork is far behind and currently shows no concrete code-level advantage.

Choose this fork only if you want a static snapshot. If you want the current agent harness with the latest fixes and workflow improvements, upstream is the better choice.