Voice
Lossless Codex Orchestrator LCO
By Index, search, summarize, and approval-gate local Codex sessions through OpenClaw/MCP. Agent-first recall and dry-run orchestration for Codex-heavy work.
Install
npm install -gConfiguration Example
{
"mcpServers": {
"lossless-openclaw-orchestrator": {
"command": "loo-mcp-server"
}
}
}README
# 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.
[](https://www.npmjs.com/package/lossless-openclaw-orchestrator)
[](https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/actions/workflows/ci.yml)
[](https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/actions/workflows/codeql.yml)
[](LICENSE)
[](CONTRIBUTING.md)
[Setup](docs/SETUP.md) · [Contributing](CONTRIBUTING.md) · [Agent Instructions](AGENTS.md) · [Agent Skill](skills/lossless-openclaw-orchestrator/SKILL.md) · [OpenClaw Plugin](docs/OPENCLAW_PLUGIN.md) · [Security](SECURITY.md) · [Code of Conduct](CODE_OF_CONDUCT.md) · [Vision](VISION.md) · [Privacy](docs/PRIVACY.md) · [Claude Boundary](docs/CLAUDE_ADAPTER_BOUNDARY.md) · [Claim Audit](docs/CLAIM_AUDIT.md) · [Release Notes](docs/RELEASE_NOTES_1.0.0.md) · [License](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](CONTRIBUTING.md).
If you are an agent working in this repository, read [AGENTS.md](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
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:
```bash
npm install -g lossless-openclaw-orchestrator@latest
loo doctor
```
Beta train, when you explicitly want the newest prerelease:
```bash
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](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:
```bash
export LOO_DB_PATH="$HOME/.openclaw/lossless-openclaw-orchestrator/orchestrator.sqlite"
```
Index local Codex sessions:
```bash
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:
```bash
export LOO_LCM_DB_PATHS="$HOME/.openclaw/lcm.db"
```
Check local readiness:
```bash
loo doctor
loo onboard status --strict
```
## First Workflow
Search for a session:
```bash
loo search "billing bridge proposed plan"
```
Describe a result:
```bash
loo describe codex_thread:<thread-id>
```
Expand a bounded brief:
```bash
loo expand-ref --profile brief --token-budget 1000 codex_thread:<thread-id>
```
Expand from a query when you do not know the ref yet:
```bash
loo expand-query --profile brief --token-budget 1000 "billing bridge"
```
For normal agent workflows, use the MCP/OpenClaw tools:
- `loo_search_sessions`
- `loo_describe_session`
- `loo_expand_session`
- `loo_codex_plans`
- `loo_codex_final_messages`
- `loo_codex_touched_files`
- `loo_codex_control_dry_run`
`loo_codex_control_dry_run` returns the audit id and hashes an agent should show
before any live resume/send/steer/interrupt call. Live control requires the
matching `approval_audit_id`.
The packaged agent playbook is
[skills/lossless-openclaw-orchestrator/SKILL.md](skills/lossless-openclaw-orchestrator/SKILL.md).
## OpenClaw And MCP
Run the MCP server directly:
```bash
loo-mcp-server
```
Typical MCP client entry:
```json
{
"mcpServers": {
"lossless-openclaw-orchestrator": {
"command": "loo-mcp-server"
}
}
}
```
Install the OpenClaw plugin from npm:
```bash
openclaw plugins install lossless-openclaw-orchestrator@latest
openclaw plugins list --json
```
Verify the package and OpenClaw gateway path:
```bash
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](docs/SETUP.md) and
[docs/OPENCLAW_PLUGIN.md](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
- dry-run plus matching `approval_audit_id` before live Codex control
Not claimed:
- full Claude Code parity
- cloud sync
- unattended desktop takeover
- permission bypass
- enterprise or customer-ready security claim
- generic GUI mutation is not supported
- Codex GUI mutation is not a stable public claim
Claude Code support is an adapter stub and redacted fixture inventory until its
storage and control paths are proven. Desktop fallback surfaces report
readiness, blockers, and proof states; they do not authorize prompt typing,
clicking, refresh/restart automation, or arbitrary app control.
Claude adapter proof boundaries live in
[docs/CLAUDE_ADAPTER_BOUNDARY.md](docs/CLAUDE_ADAPTER_BOUNDARY.md). Public
claim details live in [docs/CLAIM_AUDIT.md](docs/CLAIM_AUDIT.md).
Privacy details live in [docs/PRIVACY.md](docs/PRIVACY.md) and
[docs/SAFE_SUMMARIES.md](docs/SAFE_SUMMARIES.md).
## Community And Contributing
LCO is meant to be easy to try and safe to improve. The public contribution
path is:
1. Read [CONTRIBUTING.md](CONTRIBUTING.md) for issue routing, validation,
evidence, and agent-authored PR expectations.
2. Follow [docs/SETUP.md](docs/SETUP.md) for local install and first-run setup.
3. Use [AGENTS.md](AGENTS.md) when a coding agent is making or reviewing the
change.
4. File a bug, docs bug, feature request, adapter request, protocol drift
report, or unsafe-control report through the GitHub issue forms.
Good first issue candidates are docs gaps, redacted fixture coverage, setup
diagnostics, issue-template improvements, and narrow CLI help fixes. Use the
adapter request form to request an adapter; describe the target app/runtime,
read/index path, control boundary, and redacted proof available to test it.
Never paste raw Codex transcripts, private SQLite databases, tokens, cookies,
connector URLs, or customer data into public issues or PRs. Use
[SECURITY.md](SECURITY.md) for private vulnerability reports and
[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for community expectations.
## Architecture
- `packages/core`: SQLite index, Codex import, safe summaries, source refs,
extraction, search, and expansion
- `packages/mcp-server`: stdio MCP server exposing `loo_*` tools
- `packages/openclaw-plugin`: OpenClaw plugin entry and manifest surface
- `packages/cli`: `loo` CLI for setup, indexing, recall, smoke, eval, and
release gates
- `packages/adapters`: Codex transport, audit, redaction, CUA/Peekaboo
readiness, and adapter boundaries
- `skills/`: packaged agent-facing OpenClaw playbook
- `evals/`: scenario and scorecard contracts
- `docs/`: setup, privacy, release proof, source authority, adapter boundaries,
and deeper operator guides
## Roadmap And Proof Status
The stable public product is Codex-first local orchestration: index, search,
describe, expand, OpenClaw/MCP tools, and approval-gated dry-run/live-control
boundaries.
Current deeper product work is tracked in GitHub issues and summarized in
[VISION.md](VISION.md). Keep sprint and agent-operator details there, in
[AGENTS.md](AGENTS.md), and in the packaged
[agent skill](skills/lossless-openclaw-orchestrator/SKILL.md), not in this
public landing page.
## Maintainer Proof
Release and readiness proof lives in the runbooks, not in the first-run setup
path:
- [Release Checklist](docs/RELEASE_CHECKLIST.md)
- [Release Runbook](docs/BETA_RELEASE_RUNBOOK.md)
- [Claim Audit](docs/CLAIM_AUDIT.md)
- [QA Demo](docs/BETA_RELEASE_DEMO.md)
For `1.0`, the general release checklist requires fresh
... (truncated)
voice
Comments
Sign in to leave a comment