{"repo":"100yenadmin/Lossless-Codex-Orchestrator-LCO","free":true,"listed":false,"github":"https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO","clone":"git clone https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO.git","description":"Index, search, summarize, and approval-gate local Codex sessions through OpenClaw/MCP. Agent-first recall and dry-run orchestration for Codex-heavy work.","language":"TypeScript","stars":38,"topics":["ai-agents","codex","lcm","lossless","openclaw","orchestrator","lossless-codex","agent-tools","ai-coding-assistant","codex-cli"],"license":null,"category":"workflow-automation","readme_excerpt":"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. 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 wha","default_branch":null,"files":null,"tree":[],"storefront":"/r/100yenadmin","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/100yenadmin/Lossless-Codex-Orchestrator-LCO/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}