A LIGHT PORT OF OMO'S HEPHAESTUS, FOR CODEX
The Hephaestus deep-worker agent, ported light into Codex.
A focused slice of OmO — goals not recipes, verified completion.
Ultrawork, live
Include ultrawork (or the short alias ulw) anywhere in your prompt and the harness switches to maximum-precision, outcome-first, evidence-driven orchestration. An agent saying it is done does not mean the work is done — the work is done when observable evidence verifies it.
ulw add authentication“Plan, execute, verify, and keep the evidence attached.”
ulw add authenticationULTRAWORK MODE ENABLED!
Research wave · Explorer and Librarian gather source truthtask(subagent_type="explorer") + task(subagent_type="librarian")Root does not guess. Explorer reads the local implementation, Librarian checks docs and contracts, and their findings become the input to the Plan agent.
npx lazycodex-ai install= npx --yes --package oh-my-openagent omo install --platform=codex
$ulw-loop "task" [--strategy=reset|continue]A self-referential loop that runs until VERIFIED completion.
$ulw-plan "what to build"Prometheus strategic planner — turns an idea into a decision-complete work plan.
$start-work [plan] [--worktree <path>]Executes a Prometheus plan until every checkbox is done.
What LazyCodex wires into Codex
LazyCodex installs OmO as a serious agent harness for complex repositories: project memory, planning, execution, skills, hooks, model routing, and verification defaults in one pass.
$init-deep generates hierarchical AGENTS.md context so agents start from local guidance before touching a large repository.
$ulw-plan turns ambiguous work into a decision-complete plan, then $start-work executes it with durable progress tracking.
$ulw-loop keeps complex work moving until the completion promise is backed by verification, not a hopeful status update.
Skills auto-activate when a task matches their domain, so you do not need to study every one first. Add a skill name to your prompt when you want to call it explicitly; ulw-research is the maximum-saturation mode for deep codebase, web, official-docs, and OSS-repo research.
Team Mode
One leader, durable state on disk. The main session is always the team leader: it splits the work and assigns each slice, holds live situational awareness of every member, verifies and QAs what they deliver, relays findings between members, and synthesizes the result.
Members are defined by a concrete part, ownership area, or perspective — never a vague job role.
A bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual.
Sent by Codex from another thread
Member A COMPLETE verification note: report exists, pinned-link check passed, and no GitHub mutations/repo edits.
$ulw-research
Parallel explore and librarian swarms across the codebase, web, official docs, and OSS repos; a recursive expand loop driven by the leads workers return; empirical verification by running code; cited synthesis and optional reports.
Activates only on an explicit demand for research — say ulw-research or any ulw research wording in your prompt. While active, exhaustive coverage is the goal.
Where it comes from
OmO is the full agent harness — a primary orchestrator, a deep worker, specialist agents, multi-model routing, and dozens of lifecycle hooks. LazyCodex does not ship all of that. It ports one role, Hephaestus, into Codex as a focused, repeatable setup: the deep worker plus the workflows that keep its runs honest.
Give it a goal, not a recipe
Named after the Greek god of the forge. Methodical, thorough, obsessive. Fires parallel explore subagents before writing any code, then runs a tight loop until the work is proven. Built for deep architectural reasoning, complex debugging, and cross-domain synthesis.
Explore
Map the terrain — read with tools, never speculate.
Plan
Chart the course — files to change, specific edits, dependencies.
Implement
Build with precision — surgical edits that match codebase style.
Verify
Prove it works — LSP diagnostics, tests, build, in parallel.
Manually QA
Drive the real surface — HTTP, tmux, browser — then report.
For when good enough isn't.
Install the Codex setup, then run the workflows that keep large changes under control.