Oh My Openagent

Strengths. OmO's differentiating piece is the routing layer. Rather than forcing one model to do planning, writing, visual work, and cheap gate reviews, it assigns each category — architect, visual-engineering, ultrabrain, deep, artistry, quick, unspecified-low, unspecified-high, writing — to a model tuned for it. The tuned system prompts shipped per model mean you don't have to know that Claude Fable 5.1 is the planning pick or that Kimi K3 is the deep-work pick; you set `model_profile` in omo.json and OmO walks the chain, applies the first model your providers serve, and prints which rungs it skipped. The precedence is clear: a `--model` flag wins, then a pinned model (anything with a `/`), then a profile, then Senpi's own default. Second, the Kibitzer loop is the kind of thing most harnesses skip. A small cheap model sits beside the expensive one, reads your prior sessions, and injects a nudge — "last time this broke production, run the migration test first" — before the main agent repeats a mistake. It's read-only and it only nudges, which keeps it from becoming another source of drift. Third, the skills system loads only what the task needs instead of stuffing a giant prompt. Frontend, debugging, ulw-research, data-scientist, git-master, ultimate-browsing, imagegen, visual-qa, ast-grep, review-work, prompt-engineering, lsp-setup — each is injected per task. Combined with tool-call absorption and tool-call correction, fewer turns are wasted on malformed arguments and redundant reads. Weaknesses. The CLI-first posture is a real constraint. If your workflow is a GUI IDE plugin or interactive pair-programming back-and-forth, this isn't the shape you want. The docs also flag a known failure mode directly: over-orchestration on small bounded tasks. If your job is a two-line fix, the graph costs more than it saves. The beta status matters. Senpi standalone is the current path to running `omo` without a host, and beta means expect edges. Model availability depends on what providers you've connected, so the advertised mix is a ceiling, not a floor — a single-provider shop loses the whole routing argument. Where it fits. Developers and small teams facing multi-file migrations, deep research over thousands of sources with a claim graph and cited report, ML pipelines, or a presentable deck. Anyone who would rather describe a job once and let it drive to completion than babysit turn by turn. Where it doesn't. Beginners who want a GUI, tiny codebases where orchestration overhead exceeds the task, and interactive pair-programming flows. Teams that need Slack-native agent control today should note the messaging integrations are still being wired in one at a time.