AI & Agents
LazyCodex
Source: code-yeongyu/lazycodex · ★ 3061 · TypeScript
Last updated 2026-08-02 · benchmark measured 2026-11-05 — deterministic & reproducible
Agent harness that brings goal-driven, verified task execution to OpenAI Codex.
LazyCodex at a glance
LazyCodex is an agent harness that adds goal-driven, verified task execution to OpenAI Codex for developers working on complex codebases.
Good for
- Working through large or complex codebases that need deep research before changes
- Tracking multi-step development work across sessions with durable progress state
- Coordinating multiple Codex threads as a team on related issues or PR reviews
Questions people ask
What does LazyCodex actually do?
It installs a structured multi-agent orchestration layer into Codex that breaks work into goals, runs parallel subagents for planning, execution, and testing, and only marks a task complete once observable evidence confirms it.
How do I install LazyCodex?
You run npx lazycodex-ai install, which installs OmO with the platform set to Codex.
What is 'ultrawork mode'?
Ultrawork (or its alias 'ulw') is a maximum-precision, outcome-first mode that fans out research to Explorer and Librarian subagents, plans with a Plan agent, executes with strict TDD, and verifies completion before ending, up to 500 iterations.
What is Team Mode?
Team Mode runs a named group of cooperating Codex threads with one leader that splits work, assigns it to members with specific ownership areas, tracks their status, verifies and QAs their output, and synthesizes results, using state stored in .omo/teams.
Is LazyCodex the same as OmO?
No, LazyCodex is a light port of one part of OmO called Hephaestus, the deep worker agent, along with its plan/execute/verify workflows and Codex-specific skills and hooks; it does not include OmO's full harness such as the Sisyphus orchestrator, all specialist agents, or multi-model routing.
Written by Legit.Show from lazycodex.ai on 2026-09-30. It does not change the score.
Are you the maker of LazyCodex? Claim this listing. It is free, takes a meta tag, a DNS record or GitHub admin rights, and never changes the score.
Launched something? Add your product, free.
To cite this score: legit.show/s/gh-code-yeongyu-lazycodex/2026-11-05. That address never changes; this page moves with every re-measure.
Legit.Show scored LazyCodex 78/100 on 2026-11-05, measured across all 7 frames from its public surface. legit.show/s/gh-code-yeongyu-lazycodex/2026-11-05
Is LazyCodex production-ready?
Legit.Show scores LazyCodex 78 out of 100 — the simple average of its 7 measured frames. Legit.Show ran its deterministic 7-Frame production-readiness benchmark on LazyCodex (public-surface assessment), measured from the public surface with no LLM in the scoring path. Its strongest frame is Accessibility; its weakest is Privacy. Every frame it averages is published with its evidence on the Legit.Show listing.
The 7 Frames
- Performance — 99/100
- Accessibility — 100/100
- Security — 25/100How this compares across the catalogue: The Web Security Baseline
- Privacy — 25/100How this compares across the catalogue: The Privacy Gap
- Reliability — 100/100
- Standards — 100/100
- Discoverability — 100/100
What we measured
- No Content-Security-Policy and no HSTS.
- Served over HTTPS with a valid certificate.
- Real Lighthouse performance run — 1193 ms to first byte.
- Returns a proper 404 for unknown routes.
- 2 of 2 sampled routes reachable.
- No privacy policy found.
- Sets cookies / loads scripts with no consent prompt.
- Discoverable: structured data, sitemap, OpenGraph image, canonical URL.
Who it's for
Software developers · Engineering teams · Codebase maintainers · AI agent users
Sources and updates
- Description
- Taken from lazycodex.ai's own website on 2026-08-02.
- Code
- github.com/code-yeongyu/lazycodex.
- Benchmark
- Measured by Legit.Show from the live site, the way any visitor sees it — with no access to its code or accounts. Same method for every product, and no AI decides the score. Last checked 2026-11-05.
Put together from public information, without LazyCodex's involvement. If anything here is wrong, tell us and a person will check it.
Visit LazyCodex → · Alternatives to LazyCodex → · How this was measured →