CLI

LazyCodex provides one CLI: the lazycodex-ai npm bin. It installs and diagnoses the OmO-based Codex light setup. There is no global install; always invoke it through npx.

Forwarding to OmO

The bin reads arguments and forwards them to oh-my-openagent. The install subcommand is special-cased to pin the Codex platform; everything else passes through.

npx lazycodex-ai install

npx --yes --package oh-my-openagent omo install --platform=codex

npx lazycodex-ai install --no-tui --codex-autonomous
# -> npx --yes --package oh-my-openagent omo install --platform=codex --no-tui --codex-autonomous

npx lazycodex-ai <args...>
# -> npx --yes --package oh-my-openagent omo <args...>

--dry-run

Put --dry-run as the first argument to print the resolved npx command instead of running it:

npx lazycodex-ai --dry-run install --no-tui --codex-autonomous

Output:

npx --yes --package oh-my-openagent omo install --platform=codex --no-tui --codex-autonomous

--dry-run is stripped before forwarding, so the remaining arguments resolve exactly as they would in a real run. Use it to confirm the exact omo invocation before executing.

doctor

npx lazycodex-ai doctor

Prints a health report explaining what is configured, what is missing, and why. It checks plugin cache, hooks, MCP Servers, Agent Roles, and Codex config state. Run it first when hooks are pending, skills are not loading, or routing looks wrong.

Marketplace Alternative

The npx install is the primary path. As an additive experimental path, you can install the plugin from Codex.

codex plugin marketplace add https://github.com/code-yeongyu/lazycodex
codex plugin add omo@sisyphuslabs

Approve the omo hooks in the next Codex startup review. The first approved session runs background bootstrap and tells you to restart when it completes. Upgrade with:

codex plugin marketplace upgrade sisyphuslabs

After upgrade, plugin files changed, so trust hashes must be re-approved and hooks appear as Modified. Approve them again; the next session runs bootstrap for the new version.

Exit Behavior

The bin spawns the resolved command with inherited stdio and exits with that command's status code. If spawning npx itself fails, it prints the error and exits non-zero.

In-session Commands

Once installed, LazyCodex registers OmO commands inside Codex. These are not shell commands; they are $command entries typed in the Codex composer. Syntax and usage flow live in Commands.

Related