[!NOTE]
[OmO] 60K Stars: the terrifying token burner has arrived in LazyCodex.
Sisyphus Labs' OmO is the quality-obsessed agent harness whose public lore says it loved Anthropic models hard enough to get third-party clients blocked. Now that same OmO quality bar is available for Codex through LazyCodex.
If you wanted OmO but did not want the setup ceremony, start here:
npx lazycodex-ai install
Context: OmO 60K Stars on X
🚀 Install
One line. No global install, no npm i -g. Always use npx:
npx lazycodex-ai install
This is shorthand for npx --yes --package oh-my-openagent omo install --platform=codex. For a fully autonomous, no-TUI setup:
npx lazycodex-ai install --no-tui --codex-autonomous
Install from the Codex marketplace (experimental)
The npx installer above stays the primary path. As an additive, experimental
alternative you can install from inside Codex itself: type /plugins, open the
Add Marketplace tab ("Add a marketplace from a Git repo or local root."),
and enter https://github.com/code-yeongyu/lazycodex, then install omo from
the sisyphuslabs marketplace. Or from the CLI:
codex plugin marketplace add https://github.com/code-yeongyu/lazycodex
codex plugin add omo@sisyphuslabs
On the next launch, approve the omo hooks in Codex's startup review — hooks
never run before approval. The first approved session prints
LazyCodex bootstrap running in background — restart the session when it completes
while a background worker finishes the setup (config blocks, agent roles, bin
links, a pinned sg binary for the ast_grep MCP); restart when it is done.
The marketplace path never touches Codex permission settings — autonomous mode
remains the explicit npx lazycodex-ai install --no-tui --codex-autonomous
choice.
Upgrade with codex plugin marketplace upgrade sisyphuslabs. The next startup
review shows the hooks as Modified — expected after every upgrade —
re-approve them and the following session re-runs bootstrap on the new version.
If anything looks pending or degraded, npx lazycodex-ai doctor explains what
and why. Full details: lazycodex.ai/docs.
Verify it worked
npx lazycodex-ai doctor
doctor prints the installation health report: plugin cache, hooks, MCP
servers, agents, and config state. Inside Codex, type $ in the composer to
browse every installed skill — init-deep, ulw-loop, ulw-plan,
start-work, and the rest — and hooks announce themselves with
LazyCodex(<version>): ... status messages during a session.
Uninstall
npx lazycodex-ai uninstall
Removes the installed plugin cache, bin links, agent roles, and the managed
sections of ~/.codex/config.toml.
⚡ Commands
LazyCodex installs these as OmO commands for Codex. Invoke them with the
$command syntax shown by the installer.
| Command | Type this | What it does |
|---|
$ulw-loop | $ulw-loop "task" [--completion-promise=TEXT] [--strategy=reset|continue] | Self-referential loop that runs until Oracle-verified completion. Caps at 500 iterations in ultrawork mode, 100 in normal mode. |
$ulw-plan | $ulw-plan "what to build" | Prometheus strategic planner. Writes a plan to plans/<slug>.md. Never writes product code. |
$start-work | $start-work [plan-name] [--worktree <path>] | Executes a plan until every checkbox is done. Prints ORCHESTRATION COMPLETE. |
Full documentation lives at lazycodex.ai/docs.
Use the built-in workflows
LazyCodex should be judged by the features it actually installs. It is the
Codex distribution for OmO's agent harness: project memory, planning,
execution, verified completion, skills, hooks, model routing, and diagnostics.
1. $init-deep creates project memory
$init-deep generates hierarchical AGENTS.md context. It scores complex
directories, writes local guidance near the code that needs it, and gives future
agents landmarks before they edit. Type $init-deep in the Codex composer —
the $ prefix is how every installed skill is invoked.
Use it when the repository is too large to explain from memory. Run it again
when the shape of the codebase changes.
2. The three command pillars stay up front
Use $ulw-plan when the work needs decisions before implementation. It writes a
plan to plans/<slug>.md and does not touch product code.
Use $start-work when a plan is ready. It executes the checklist with durable
Boulder progress and stops only when the plan is complete.
Use $ulw-loop when the task should keep moving until the result is verified by
evidence instead of a hopeful status update.
3. Skills cover specialized work
The command layer stays simple. The skill layer adds specialist judgment for the
actual work:
| Feature | Use it for |
|---|
$init-deep | Hierarchical project memory through AGENTS.md |
$ulw-plan | Decision-complete planning before code changes |
$start-work | Durable plan execution with Boulder progress |
$ulw-loop | Verified completion for open-ended tasks |
review-work | Multi-angle post-implementation review |
remove-ai-slops | Behavior-preserving cleanup of AI-looking code |
frontend-ui-ux | Polished UI surfaces |
programming | Strict TypeScript, Rust, Python, or Go discipline |
LSP | Diagnostics, definitions, references, symbols, and renames |
AST-grep | Structural search and rewrite across code |
rules | Project instructions from AGENTS, rules, and instruction files |
comment-checker | Feedback after edit-like operations |
This is the beginning of the README. Read the rest at the original. Read the full README ↗
