AI tool comparison
oh-my-codex vs qmd
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
oh-my-codex
Add AI agent teams, event hooks, and a live HUD to any Git repo
75%
Panel ship
—
Community
Free
Entry
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.
Developer Tools
qmd
Local doc search engine with BM25 + vectors + LLM re-ranking — by Shopify's CEO
50%
Panel ship
—
Community
Free
Entry
qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.
Reviewer scorecard
“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.”
“Hybrid BM25 + vector + LLM re-rank is the right architecture for personal knowledge search — each layer catches what the others miss. The MCP server mode is genuinely useful: being able to ask Claude Code 'what did we decide about X last month' against my own notes changes the workflow. MIT licensed and from someone who ships real products.”
“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.”
“This is a well-executed weekend project, not a production tool. It requires GGUF models and manual embedding setup — a meaningful friction barrier for non-technical users. The 'built by a CEO' narrative drives GitHub stars more than the technical differentiation. Obsidian with a local AI plugin gets you here with better UX.”
“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.”
“The pattern here — local hybrid retrieval as an MCP server feeding into AI coding agents — will be ubiquitous in two years. Today it's a technical power-user tool; tomorrow it's how everyone's AI assistant knows the institutional context behind the code. qmd is an early, clean implementation of that pattern.”
“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.”
“I manage a lot of notes, references, and creative briefs, but the setup friction here — GGUF models, CLI configuration — makes this inaccessible for most creators. The concept is great; the UX needs a front-end before it reaches beyond developers.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.