Skip to content

The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.

3.4 KB
Raw Blame

LazyCodex is a light port of OmO into Codex. It does not ship the full harness — it ports one role, Hephaestus, the autonomous deep worker, and the workflows that keep its runs honest. Think LazyVim for lazy.nvim, but for Codex.

"LazyVim made Neovim usable for the rest of us. LazyCodex does the same for Codex."

Thin distribution

LazyCodex itself is close to a small install alias. lazycodex-ai runs the OmO installer targeting the Codex platform, and the actual features come from the omo plugin.

What gets installed

Layer What it means in Codex
Commands $init-deep, $ulw-plan, $start-work, $ulw-loop — workflow entry points.
Skills Review, debugging, refactoring, frontend, LSP, rules injection, and more — specialist playbooks.
Hooks Automatic assistants that fire at session start, prompt submit, post-edit, post-compact, and stop.
MCP Servers grep_app, context7, codegraph, git_bash, lsp — tool connections.
Model routing Role-based model profiles so planning, implementation, and verification each get the right model.
Agent roles explorer, librarian, plan, momus, metis, and executor/reviewer roles for subagent delegation.

Where it comes from

OmO is the full agent harness: a primary orchestrator (Sisyphus) with .omo/boulder.json session continuity, a deep worker (Hephaestus), specialist agents, multi-model routing, 54+ lifecycle hooks, and team mode. That is a lot. LazyCodex takes only the piece that matters for a focused Codex setup and packages it as a repeatable install.

What you get

The Hephaestus deep worker, ported into Codex with:

  • Goal-oriented execution — you give it objectives, not step-by-step recipes.
  • A tight operating loop: Explore → Plan → Implement → Verify → Manually QA.
  • Parallel explore subagents so it maps the terrain before writing anything.
  • The $ulw-plan, $start-work, and $ulw-loop workflows that keep complex work moving until it is verified.
  • Skills, hooks, model routing, and verification defaults wired into Codex in one pass.

Remember these four

  1. $init-deep creates project memory.
  2. $ulw-plan "what to build" sets the work order.
  3. $start-work executes the plan.
  4. $ulw-loop "task" keeps going until verified.

LazyCodex wires rules loading, skills, hooks, model routing, and verification habits around this flow. Browse the sidebar docs one section at a time when you need the details.

The harness workflow

Use {your prompt} ultrawork when the job needs the deep worker to run as one coordinated, evidence-bound loop instead of a single turn.

How it fits together

LazyCodex is a thin distribution layer over OmO. The core engine is OmO; LazyCodex packages OmO's Hephaestus for Codex.

Credit: The LazyCodex name idea is inspired by LazyVim. The Ultragoal and UltraQA ideas are inspired by oh-my-codex, reimplemented from concept for this Codex setup.