O

oh-my-codex

Add AI agent teams, event hooks, and a live HUD to any Git repo

PriceOpen Source / FreeReviewed2026-04-07

Expert verdict

Ship

3-1
3 Ships1 Skips
Visit github.com

The Panel's Take

oh-my-codex (OMX) is a lightweight open-source tool that bolts AI capabilities onto any Git repository via three primitives: hooks (event-driven automations triggered by commits, PRs, or file changes), agent teams (configurable multi-agent crews for specific tasks like code review or documentation), and a HUD (a heads-up display showing what agents are doing and what they've changed in real time). Built by indie developer Yeachan-Heo, the project emerged from frustration with AI coding assistants that require full IDE integration. OMX is editor-agnostic — it runs as a background process, listens to repository events, and dispatches agent work asynchronously. The HUD can be run in any terminal alongside your existing workflow. The project trended on GitHub around April 4 and has generated interest from developers who want AI automation at the repository level rather than the editor level. The hooks system in particular maps cleanly to CI/CD mental models, making it feel familiar to developers who already think in terms of repository events.

Share this verdict

oh-my-codex verdict: SHIP 🚀

3 ships · 1 skip from the expert panel

Full review: shiporskip.io/tool/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation

Weekly AI Tool Verdicts

Get the next verdict in your inbox

7 critics review a new AI tool every day. Weekly digest — free.

Looking for oh-my-codex alternatives?

Compare oh-my-codex with every other Developer Tools tool reviewed by our panel.

See all Developer Tools alternatives

Embed this verdict

Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.

Ship · 7.5/10
HTML badge
<a href="https://shiporskip.io/api/badge-click/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation" alt="oh-my-codex Ship verdict on ShipOrSkip" width="360" height="90" /></a>
Markdown badge
[![oh-my-codex Ship verdict on ShipOrSkip](https://shiporskip.io/api/badge/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation)](https://shiporskip.io/api/badge-click/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation)
Iframe widget
<iframe src="https://shiporskip.io/embed/oh-my-codex-github-hooks-ai-agent-teams-hud-repo-automation" title="oh-my-codex ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>

The reviews

This is the right abstraction layer — repo-level AI hooks that work regardless of what editor you're in. The HUD is surprisingly polished for an indie project. I can see this becoming a standard part of the dotfiles setup for developers who work across multiple editors.

Helpful?

The hooks and agent teams concept is compelling but the execution feels early. Agent teams with no guardrails running on every commit is a recipe for noise and unintended changes. Until there's robust configuration for when NOT to fire agents, this needs careful testing before use on anything production-adjacent.

Helpful?

The HUD pattern — a live display of autonomous agents working in your codebase — is a glimpse at how software development will feel in two years. When agents are good enough to be trusted, you'll want exactly this: a terminal showing what they're doing while you think about the next problem.

Helpful?

I'd use the hooks to auto-update documentation on every commit and have the HUD show me what changed in plain English. The editor-agnostic approach means it works the same whether I'm in Cursor, Zed, or vim — that flexibility matters a lot for creative workflows.

Helpful?

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later