Lossless Claw Conflicts with OpenClaw 2.0; Disabling Restores Long-Task Stability

Upgrading OpenClaw to 2.0 broke a long-running production workflow that had been stable for hours. According to a report on r/openclaw, the culprit appears to be a conflict with the latest version of Lossless Claw. Disabling it, along with tweaks to the PRD file, got things moving again.

What Happened

The user runs an 8-hour cycle that combines heavy video work with Comfy UI and LLM-based reasoning, originally using QWEN 3.5. It worked flawlessly until updating to OpenClaw 2.0, when everything came to a halt. Their analysis — via Codex — pointed to a conflict between OpenClaw 2.0 and the newest Lossless Claw as a primary cause.

The Fix

The temporary solution was to disable Lossless Claw in OpenClaw 2.0. This required additional modifications to the PRD file logic, but after those changes the workflow resumed. At the time of the post, the user was 31 minutes into a new test run with no issues.

Why Lossless Claw Matters

The user notes that despite the conflict, Lossless Claw is crucial for building coherent, long-running tasks. After re-enabling it earlier had made a noticeable difference, but its full value became apparent only after disabling it. They've submitted a ticket to address the conflict, but the report serves as a cautionary tale for relying on version-compatible combinations of agent tools.

For developers running similar long tasks, this suggests checking tool compatibility before upgrading and being prepared to temporarily disable extensions to isolate the issue.