Lossless OpenClaw Orchestrator

LCO turns local Codex sessions into searchable, bounded, approval-aware work objects for OpenClaw.

Use it when an agent or user needs to answer: what sessions are active, what did they plan, what did they finish, what files did they touch, and what is the next safe action without rereading raw transcripts.

Setup · Contributing · Agent Instructions · Agent Skill · OpenClaw Plugin · Security · Code of Conduct · Vision · Privacy · Claude Boundary · Claim Audit · Release Notes · 1.2.0 Notes · 1.1.4 Notes · 1.0 Notes · License

Why It Matters

Codex is powerful, but long-running local work can become hard to supervise once you have dozens or hundreds of threads. LCO gives your orchestrator agent a safe operating picture: search first, inspect compact session cards, expand only bounded evidence, and dry-run the next action before anything live happens.

If you are here to contribute, start with CONTRIBUTING.md. If you are an agent working in this repository, read AGENTS.md before editing files.

What It Does

LCO is a local-first orchestration layer for Codex-heavy work:

• indexes local Codex session stores into a local SQLite database
• searches sessions by safe summaries, plans, finals, touched files, and refs
• describes one session without exposing the whole transcript
• expands only the evidence an agent needs, with token-budgeted profiles
• exposes loo_* tools through MCP and the OpenClaw plugin
• creates dry-run approval packets before Codex resume/send/steer/interrupt
• reports Codex Desktop visibility and fallback readiness without GUI mutation
• validates exact action-bound Desktop collaboration proof packets without executing them
• summarizes runtime Desktop visibility coverage and next read-only proof steps
• classifies active threads as running, blocked, needs-nudge, stale, waiting, approval-needed, idle, or unknown from public-safe read-only signals, including attention coverage, non-executed read-only probe recommendations, and non-executed control dry-run recommendations for safe nudge handoff
• plans one deterministic read-only autonomy loop tick with execute:false tool calls so an agent can probe before dry-run handoff without mutation

The result is a staged recall loop:

1. Search broadly.
2. Describe the likely session.
3. Expand a small evidence bundle.
4. Dry-run the next action.
5. Execute only after the user approves the exact target/action.

Install

Requirements:

• Node.js 22 or newer
• npm
• local Codex session files, usually under ~/.codex/sessions
• OpenClaw Desktop/CLI if you want installed loo_* tools through OpenClaw

Stable install:

npm install -g lossless-openclaw-orchestrator@latest
loo doctor

Beta train, when you explicitly want the newest prerelease:

npm install -g lossless-openclaw-orchestrator@beta

Package channels:

• latest is the stable public channel.
• beta is the active prerelease train.
• next is reserved for release candidates.

Full first-run instructions live in docs/SETUP.md.

Set Up

Choose where LCO stores its local index. The default is already under ~/.openclaw, but setting it explicitly makes setup easier to inspect:

export LOO_DB_PATH="$HOME/.openclaw/lossless-openclaw-orchestrator/orchestrator.sqlite"

Index local Codex sessions:

loo index codex --max-files 500 "$HOME/.codex/sessions" "$HOME/.codex/archived_sessions"

Optional: allow read-only recall from one or more OpenClaw LCM peer databases:

export LOO_LCM_DB_PATHS="$HOME/.openclaw/lcm.db"

Check local readiness:

loo doctor
loo onboard status --strict

If agents will author PRs, issue comments, or closeouts in the repo, also copy the provenance snippets from docs/SETUP.md into the repo's AGENTS.md and CLAUDE.md files.

First Workflow

Search for a session:

loo search "billing bridge proposed plan"

Describe a result:

loo describe codex_thread:<thread-id>

Expand a bounded brief:

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

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

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

For normal agent workflows, start with the compact public/operator facade instead of treating every loo_* tool as a peer:

Other declared tools remain available as workflow_detail, proof_debug, or internal_low_level surfaces for setup, diagnosis, proof, and recovery. Their existence is deliberate: normal agents should start from the facade, then drop to the lower tiers only when the compact path returns a specific next step or blocker.

loo_codex_control_dry_run returns the audit id and hashes an agent should show before any live start/resume/send/steer/interrupt call. Live control requires the matching approval_audit_id.

Live Codex control results include proof_state fields for accepted_by_transport, started, completed, persisted, and unverified_pending. Transport acceptance is not durable execution: when unverified_pending is true, run the returned next_proof read-only tool call before claiming the turn or thread completed, persisted, or is safe to build on.

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

Naming policy: LCO is the public product abbreviation and lco_* is the forward public alias target for new user-facing tool names. The currently callable OpenClaw/MCP tools still use the historical loo_* runtime prefix, so examples that must run today continue to show loo_* until #434 lands a tested alias layer. Do not delete or silently rename the loo_* tools; keep them as backward-compatible aliases when lco_* aliases are added.

OpenClaw And MCP

Run the MCP server directly:

loo-mcp-server

Typical MCP client entry:

{
  "mcpServers": {
    "lossless-openclaw-orchestrator": {
      "command": "loo-mcp-server"
    }
  }
}

Install the OpenClaw plugin from npm:

openclaw plugins install lossless-openclaw-orchestrator@latest
openclaw plugins list --json

Verify the package and OpenClaw gateway path:

loo openclaw dogfood --profile lco-dogfood --install-source lossless-openclaw-orchestrator@latest --required-tool loo_doctor --required-tool loo_search_sessions --strict
loo openclaw tool-smoke --profile lco-dogfood --required-tool loo_doctor --required-tool loo_search_sessions --strict

OpenClaw gateway setup may require local credential, device-pairing, token, or scope approval steps before tool smoke can pass. LCO reports those as setup blockers, not package failures. See docs/SETUP.md and docs/OPENCLAW_PLUGIN.md.

Safety Boundaries

LCO is Codex-first and local-first.

Default behavior:

• local SQLite index
• public-safe summaries before raw expansion
• source refs instead of raw transcript paths
• bounded expansion profiles
• read-only OpenClaw LCM peer DB access
• direct Codex protocol before desktop fallback
• CUA Driver as the preferred/default des