Lossless Codex Orchestrator

Give your main agent a memory and command layer for all your Codex projects and threads.

Codex is excellent at doing work. The hard part is managing all the work after you have dozens or hundreds of threads across repos, customer projects, fixes, reviews, and follow-ups.

LCO turns that scattered local Codex history into an operating layer your Hermes agent, MCP client, OpenClaw agent, or custom agent can use. Your agent can find the right project, understand what happened, see what is blocked, prepare the next action, and keep moving without rereading huge transcripts every time.

npm install -g lossless-codex-orchestrator@latest
lco doctor
lco find "billing bridge"

If this helps your main agent stay on top of Codex work, a star helps other agent builders find it. ⭐

Setup · OpenClaw Plugin · Agent Skill · Vision · Privacy · Hermes Boundary · Contributing · AGENTS.md · Security · Code of Conduct · Release Notes · License

Why It Exists

When you use Codex heavily, the problem stops being "can an agent code?" and becomes "can my main agent understand all the work already in motion?"

LCO gives that main agent a local memory and command surface:

Without LCO	With LCO
Threads are scattered across many sessions and projects.	Your agent can search and triage them from one local index.
Every handoff starts with rediscovery.	Prepared cards show the objective, blocker, status, and next action.
Big transcripts eat context.	Summary leaves and bounded expansion let agents read the right slice.
OpenClaw or another orchestrator has to guess what Codex did.	MCP/OpenClaw tools expose Codex state directly to the orchestrator.
"Continue this work" is risky because the target may be unclear.	Dry-run command packets show the exact thread and action before anything runs.

The goal is simple: your orchestration agent should manage Codex work the way a good technical operator would. It should know the projects, the active threads, the stale work, the blocked work, the finished work, and the right next move.

What It Does ✨

LCO is more than a transcript index. It builds an agent-readable operating picture over local Codex work.

Project and thread memory

• Indexes local Codex sessions into a local SQLite database.
• Uses field-weighted FTS5 search for session-card discovery over titles, summaries, proposed plans, final messages, touched files, tool metadata, and prepared safe text. For remembered content phrases, use lco grep or lco expand-query.
• Blends relevance, recency, identifier matching, and query fallback so agents can find "the billing bridge plan" or "the PR that touched auth" without the exact thread id.
• Detects Codex JSONL format drift in lco doctor so broken imports are visible instead of silently missing work.

Prepared state for agents