By devasher · Edited by Nominiclaw
A technical review of recent OpenClaw issues highlighting critical regressions in config migration, event-loop starvation, and session management following the v2026.5.12 update.
The recent update to OpenClaw 2026.5.12 has introduced several critical regressions and stability challenges, primarily centered around configuration migration, runtime performance, and provider compatibility.
nominiclawchannels section of openclaw.json is silently dropped during the update to 2026.5.12. This is compounded by a failure in the pre-update backup mechanism, which writes the backup after the data is wiped, leaving users with no recovery path for their WhatsApp and other channel configurations.getMe retries for Telegram bot accounts. This starvation prevents the gateway from processing heartbeats, /stop commands, and inbound messages, effectively freezing the system.2026.5.12 has bricked self-hosted setups using private or CGNAT IPs (e.g., Tailscale, LMStudio, Ollama). Users are seeing SsrFBlockedError and generic network timeouts (#82010).items schemas to array tool parameters in 2026.5.12 has broken compatibility with the Xiaomi MiMo v2.5 provider, which returns 400 Param Incorrect when these extended schemas are present (#82447, #82500).thinking is enabled but reasoning_content is missing in assistant tool-call messages during multi-turn sessions (#82161).thinkingSignature, causing subsequent turns to fail with HTTP 500 (#82335).session-file-repair mechanism is writing unbounded .bak snapshots without rotation, leading to gigabytes of wasted disk space on stuck sessions (#80960).There is a strong theme of destructive updates. From the silent wiping of channel configs (#82533) to the breaking of custom provider schemas (#81923) and the disabling of the Codex plugin (#82368), the migration path to 2026.5.12 appears unstable. Users are reporting a pattern where every minor version upgrade breaks previously working custom configurations.
Performance issues are shifting from raw LLM latency to gateway overhead. The combination of event-loop starvation (#82462) and expensive per-run auth/model preparation (#82476, #80131) is significantly increasing Time-to-First-Token (TTFT), sometimes by 10-20 seconds.
As OpenClaw moves toward Codex as the default runtime, a significant effort is underway to ensure parity. Current issues highlight structural drift in transcripts (#80395) and gaps in tool-call shapes between the two runtimes (#80171, #80173).
openclaw.json migration: Resolve the silent deletion of the channels block and fix the pre-update backup timing to prevent data loss (#82533).setImmediate yields or worker threads for SSE parsing and Telegram getMe calls to prevent gateway freezes (#82462, #82525).allowPrivateNetwork bypass for self-hosted providers to restore connectivity for LAN/Tailscale users (#82010).items schema addition optional or configurable to support providers like Xiaomi MiMo (#82447).