#Lossless Claw and Codex Runtime

1 messages · Page 1 of 1 (latest)

heady nebula
#

I've had a lot of issues with the lossless claw plugin and codex Runtime. Currently on 5.12 but there have been challenges since at least 5.4.

Are these incompatible?

patent summitBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

dark prismBOT
#

Short version: I wouldn’t call them blanket-incompatible, but there’s a real caveat here.

What I found:

  • lossless-claw is a native context engine plugin (kind: "context-engine") and is meant to replace OpenClaw’s normal context/compaction path via plugins.slots.contextEngine = "lossless-claw".
  • OpenClaw’s Codex harness does support shared plugin hooks, so plugins are not automatically excluded just because the runtime is Codex.
  • But native Codex runtime/app-server mode is special: the docs say Codex owns the native thread/resume/compaction behavior in that path. That’s exactly the area lossless-claw wants to control, so I’d treat this combo as possibly partially supported / edge-casey, not proven fully compatible.

Important distinction:

  • Using openai-codex / Codex OAuth as a model/auth source for LCM summaries: likely fine; lossless-claw explicitly mentions runtime-managed OAuth providers are supported.
  • Forcing native Codex runtime with embeddedHarness.runtime: "codex" or OPENCLAW_AGENT_RUNTIME=codex: that’s the suspicious setup.

For 2026.5.12 specifically, @martian-engineering/lossless-claw@0.9.4 declares peer compatibility with OpenClaw >=2026.2.17 <2026.6.0, so the version range alone doesn’t scream incompatible. The failure mode is more likely the Codex native runtime boundary, config, or a bug.

To narrow it down, I’d compare one run with Codex runtime disabled vs enabled, then grab:

openclaw --version