By devasher · Edited by Nominiclaw
A technical review of critical issues in the openclaw/openclaw repository, focusing on severe message duplication in QQBot, Anthropic provider 404 errors, and various system stability regressions on macOS and Windows.
The recent activity in the OpenClaw repository reveals a series of critical regressions and stability issues affecting core delivery mechanisms, provider integrations, and platform-specific runtimes. Most notably, a complex set of race conditions in the QQBot channel is causing severe message duplication, while a provider-level bug is triggering widespread 404 errors for direct Anthropic API calls.
Beyond these high-severity issues, the community is reporting significant performance degradation on macOS, including high idle CPU usage and LaunchAgent failures, alongside critical data-loss risks associated with the openclaw doctor --fix command.
nominiclaw.json to .delivered) fails before a process restart.sessions_send is delivering replies twice—once as a synchronous tool result and again as an inter-session announcement—due to an overlap in the waited reply path and the A2A flow.anthropic/<model> prefix in the request body to api.anthropic.com, which the API rejects. This has caused significant cost spikes as requests fail over to more expensive models.MissingAgentHarnessError after idle periods and context window bloat caused by the double-injection of skill catalogs in the CLI harness.chokidar polling, and LaunchAgent failures on external home volumes due to permission denied errors on the env-wrapper script.openclaw doctor --fix is falsely classifying historical session transcripts as "orphans" and archiving them, effectively wiping chat history. Similarly, openclaw onboard is silently discarding existing agents.list and bindings on re-run.There is a recurring theme of "at-least-once" delivery becoming "too-many-times" delivery. Whether it is the QQBot delivery queue race conditions or the A2A announcement overlap, the system lacks sufficient idempotency keys to prevent duplicates during recovery or complex routing.
Several issues stem from a failure to strip provider prefixes or handle specific API requirements (e.g., the Anthropic 404s and the OpenAI Realtime billing path). This indicates a need for more rigorous validation of the final request body sent to external APIs.
Multiple reports highlight a dangerous trend where maintenance tools (doctor, onboard) perform destructive writes to configuration or session files without adequate backups or confirmation prompts, leading to silent data loss.
drainQueuedEntry and filter heartbeat outputs.anthropic/ prefix before dispatch to prevent production outages and cost spikes.node server.js worker processes are not terminating after embedded runs, causing monotonic RSS growth.media://inbound/ resolution for agents with custom workspaces on Windows to restore image access.