// the find
code-yeongyu/oh-my-openagent
omo/lazycodex: The coding agent for tokenmaxxers;the one and only agent harness for complex codebases. For your Codex, for your OpenCode
oh-my-openagent is a plugin/configuration layer for OpenCode (and now Codex CLI) that pre-configures multi-model agent orchestration, LSP integration, hash-anchored edits, and a library of skills and slash commands. It targets developers who find setting up coding agents from scratch tedious and want a batteries-included harness that routes work to the best available model automatically. The 60k+ stars are real, but they accumulated during a dramatic period (Anthropic blocking OpenCode), so some of that is hype gravity.
The hash-anchored edit tool (Hashline) is the most technically interesting piece — content-hashing each line before applying edits is a real solution to the stale-line failure mode that plagues most coding agents, and the 6.7% → 68.3% stat is credible given how well-documented the harness problem is. The category-based model routing (visual-engineering → one model, ultrabrain → another) is a practical abstraction that saves users from manual model juggling every task. Team Mode with tmux visualization gives you actual observability into parallel agent execution rather than a black box. The skill-embedded MCP servers that spin up on demand and scope to the task is a smart way to keep context windows from bloating.
The project is maintained by an AI (Jobdori) building itself in public, which sounds cool until you're debugging a subtle config regression at 11pm — the bus factor is essentially zero and the human reviewer's own caveat ('I don't really know TypeScript') is not reassuring. The README is half marketing copy and half technical content with no clear separation, making it genuinely hard to determine what's real vs aspirational — the vendor list ('loved by Google, Microsoft, Vercel') with zero named contacts is exactly the kind of claim that ages badly. The package naming chaos (oh-my-opencode vs oh-my-openagent vs omo, with 'do not use bunx omo it's the wrong package') is a real footgun and signals the project is moving faster than its own housekeeping. Tight coupling to OpenCode as the host harness means you're betting on that project's stability, and OpenCode itself was the reason Anthropic rate-limited the whole operation.