Lossless-Codex-Orchestrator

Install 🚀

Requirements:

• Node.js 22.5 or newer
• npm
• local Codex session files, usually under ~/.codex/sessions
• Hermes if you want the primary supported agent path over stdio MCP
• OpenClaw Desktop/CLI if you want the compatibility plugin

Stable install:

npm install -g lossless-codex-orchestrator@latest
lco doctor

lossless-codex-orchestrator is the current published npm package name. The deprecated compat package lossless-openclaw-orchestrator remains maintained for existing automation and points at the same lco CLI and lco-mcp-server. The historical loo, loo-mcp-server, and LOO_* env names remain maintained compatibility aliases for at least two minor releases.

loo index codex "$HOME/.codex/sessions"
loo-mcp-server

Beta train, when you explicitly want the newest prerelease:

npm install -g lossless-codex-orchestrator@beta

Package channels:

- npm latest and GitHub Releases are the stable publication authorities. - A version in the source tree is a candidate until those publication authorities show the same version; merged source alone is not release proof. - latest is the stable public channel. - beta is the active prerelease train. - next is reserved for release candidates. - npm dist-tags and GitHub Releases are the publication authorities; source version metadata, merged code, and local package smoke are not release proof.

If npm shows a version or dist-tag but install fails with a selector cutoff error such as ENOVERSIONS or ETARGET, use the npm selector-drift tarball fallback with raw npm commands a fresh shell can run:

tarball_url="$(npm view lossless-codex-orchestrator@latest dist.tarball)"
test -n "$tarball_url" && npm install -g "$tarball_url"

If the ETARGET message says the requested package version must have a publish date before a specific time, check for a local npm min-release-age or before pin before treating it as registry drift.

Full setup instructions live in docs/SETUP.md.

First Workflow 🧭

Find the work you remember. lco find runs a local incremental index pass on first use, then searches titles, metadata, prepared cards, summaries, and event-level content snippets:

lco find "billing bridge proposed plan"

Use JSON when you want the same result shape in scripts or agent harnesses:

lco find --json "billing bridge proposed plan"

For lower-level recall, use lco search for title/session-card discovery and lco grep or lco expand-query for content-oriented recall.

Before preparing a drive plan, ask what changed since a public-safe cursor:

lco session-diff --cursor <cursor>

Build a bounded review-then-drive packet without running live control:

lco drive --dry-run --reviewer codex --driver claude --max-turns 3

When LCM peers are configured, inspect their read-only integrity posture with lco doctor --peers. Claude targeting in 1.6 validates availability and dry-run policy only; it does not provide Claude live control.

Describe a result:

lco describe codex_thread:<thread-id>

Expand a small brief:

lco expand-ref --profile brief --token-budget 1000 codex_thread:<thread-id>

Expand from a query when you do not know the ref yet:

lco expand-query --profile brief --token-budget 1000 "billing bridge"

For an agent or MCP client, start with the normal operator path:

Lower-level dry-run, resume, send, steer, and interrupt tools remain explicit workflow-detail fallbacks; they are not extra public-facade steps.

The packaged agent playbook is skills/lossless-openclaw-orchestrator/SKILL.md.

Naming note: LCO is the public product abbreviation. New user-facing examples use lco, lco-mcp-server, and canonical lco_* tools. The historical loo, loo-mcp-server, and loo_* names remain maintained compatibility aliases for at least two minor releases.