The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.
Hooks and lifecycle are how the harness keeps a long run moving without you re-prompting every turn. OmO installs lifecycle hooks into Codex that observe each turn and decide what happens next.
Trigger matrix
| Event | What fires |
|---|---|
SessionStart |
Project rules loading, telemetry, auto-update check, bootstrap provisioning, CodeGraph bootstrap. |
UserPromptSubmit |
Project rules re-injection, ultrawork trigger detection, $ulw-loop steering. |
PreToolUse |
Git Bash MCP guidance on Bash calls, $ulw-loop goal budget protection on goal creation. |
PostToolUse |
Comment checker, LSP diagnostics, CodeGraph init guidance, apply_patch rule matching, thread title hygiene. |
Stop / SubagentStop |
$start-work continuation, LazyCodex executor evidence verification. |
PostCompact |
Git Bash notification, project rules, and LSP diagnostics cache resets. |
The core mechanism
A Stop-hook fires when a turn ends. If a plan is still in progress, the hook re-injects the next turn automatically — the agent continues from durable progress state instead of waiting for you to say "continue". The run only stops when the plan is complete or a gate fails in a way that needs a human.
Where progress lives
Progress state is written to .omo/boulder.json and survives across turns and sessions. That is what lets $start-work resume a plan after a restart, and what keeps $ulw-loop honest about how far it has actually gotten.
Approval and trust
Hooks never run before approval. On the first launch after install, Codex's startup review asks you to approve the omo hooks. After every upgrade the hooks show as Modified — expected, because the plugin files changed and the previous trust hashes no longer match — re-approve and the next session re-runs bootstrap on the new version.
Evidence gates
During execution the lifecycle enforces five evidence gates before a step can close: plan reread, automated verification, manual-QA, adversarial QA, and cleanup. A step that cannot pass its gates does not advance, regardless of what the status text claims.
Installed components
The hooks above are thin entry points into these installed components:
| Component | Responsibility |
|---|---|
rules |
Project rules at session start, prompt submit, apply_patch, and post-compact. |
bootstrap |
LazyCodex install state and provisioning checks. |
telemetry |
Session start recording. |
comment-checker |
Comment feedback after edit-like tool calls. |
lsp |
Language-server diagnostics after edit-like tool calls and cache reset after compact. |
ultrawork |
Ultrawork trigger detection at prompt submit. |
ulw-loop |
Loop steering and goal budget protection. |
start-work-continuation |
$start-work execution continuation. |
git-bash |
Git Bash MCP guidance on Bash calls and post-compact. |
codegraph |
CodeGraph bootstrap and init guidance. |
teammode |
Thread title hygiene checks. |
lazycodex-executor-verify |
Sub-agent evidence verification. |
Reading more
- ultrawork mode — the mode that turns these gates into a binding loop.
- Configuration — how to tune hook behavior and lifecycle defaults.