Discipline agents
Sisyphus orchestrates Hephaestus, Oracle, and Librarian — a coordinated AI dev team running inside Codex with parallel execution.
LazyCodex (LZX) does not run as one big prompt. It installs a small cast of discipline agents into Codex, each tuned to one job. Sisyphus reads your intent and delegates; the specialists work their lanes; the loop keeps moving until the result is verified by evidence instead of a hopeful status update.
These agents come from the OmO (oh-my-openagent) harness. LazyCodex is a thin distribution layer that packages that harness for Codex — "LazyVim for Codex."
Where the role detail comes from. The LazyCodex README only names these agents — "Sisyphus orchestrates Hephaestus, Oracle, Librarian." The per-role behavior and tool boundaries below are defined by the underlying OmO engine, not by the LazyCodex README. See the OmO agent docs for the authoritative source.
The cast
Sisyphus
Hephaestus
Oracle
Librarian
Roles at a glance
| Agent | Role | Boundary |
|---|---|---|
| Sisyphus | Orchestrator | Reads intent, splits the work, delegates to specialists, tracks todos, and only stops when the task is done. |
| Hephaestus | Implementation | The deep worker that writes code, debugs, and reasons through hard logic and synthesis. |
| Oracle | Verification & review | Read-only consultant for architecture and debugging. Verifies completion; performs no writes, edits, or delegation. |
| Librarian | Retrieval | Research-only. Pulls documentation, remote repos, and OSS code. No writes, edits, or delegation. |
The read-only boundaries on Oracle and Librarian are part of the harness. They stop a "smart" agent from doing unsafe work in the wrong role — retrieval and review never silently mutate your codebase.
How they coordinate
Sisyphus is the entry-point orchestrator: it reads intent, splits a request into units, and hands them to the right specialist.
- Hephaestus takes the implementation and hard-reasoning units.
- Oracle verifies the result and consults on architecture and debugging, read-only.
- Librarian retrieves the context (docs, repos, examples) the workers need.
Oracle and Librarian do not delegate — their tool access is read-only by design. Because delegation is explicit, multiple lanes can run at once.
Parallel execution
LazyCodex runs specialists in parallel when the main session can keep moving without a result. Independent research and self-contained units run simultaneously; work stays synchronous when a result blocks the next implementation decision. Each unit is paired with a model that fits the job — see Multi-model routing.
Where this fits
- The command pillars drive these agents:
$ulw-planplans,$start-workexecutes a plan, and$ulw-loopkeeps looping until Oracle-verified completion. - Verified completion is what makes the loop stop — see The ultrawork loop.
The ultrawork loop
How $ulw-loop drives work to Oracle-verified completion — evidence over hopeful status, iteration caps, --completion-promise and --strategy, and its place alongside $ulw-plan and $start-work.
Multi-model routing
Automatic model selection per task category — quota discipline, benchmark-driven, not random churn.