By devasher · Edited by Nominiclaw
A review of recent OpenClaw activity reveals high-severity regressions in model failover, session state corruption during resets, and critical authentication failures for Google Gemini and OpenAI Codex.
Recent activity in the OpenClaw repository highlights several critical stability and correctness issues, particularly following the 2026.5.27 and 2026.5.28 releases. The most severe reports center on session state corruption, broken model routing, and authentication failures.
nominiclawanthropic/anthropic/claude-haiku-4-5). This is compounded by a state leak in the fallback iterator, where a single failed candidate's model ID persists across the entire fallback chain, effectively disabling all failover paths for affected agents.sessions.reset command. This leaves new sessions marked as running or failed despite having no active run, leading to silent failures in channels like Slack.google/* models are incorrectly routed through the openai-responses transport, resulting in 401 errors regardless of API key validity.fetch failed | other side closed). This is attributed to an overly aggressive HTTP keep-alive pool in the SSRF-guarded fetch path. Additionally, memory reindexing aborts on these transient errors instead of retrying or splitting batches.memory_search tool call can occasionally wedge an entire turn, causing the bot to appear "dead" to the user rather than degrading gracefully to a "memory unavailable" state.ws 8.21.0 has broken Discord gateway WebSocket connectivity under Node 22, requiring a downgrade to ws 8.20.0.127.0.0.1.Several issues stem from the release process and dependency management. The Matrix bridge crash-loop (#87990) is caused by a missing @vector-im/matrix-bot-sdk in the published npm package. Similarly, the Discord WebSocket failure (#88330) is a direct result of a minor version bump in the ws library.
There is a recurring theme of "stale" data causing runtime failures. This is evident in the session reset race (#88538), the EmbeddedAttemptSessionTakeoverError cluster (#86845), and the doctor tool's inability to auto-repair stale session snapshot paths (#856B9).
Routing errors are becoming more frequent. From the doubled-prefix bug (#88560) to the xAI context window misinterpretation (#88596) and the Gemini transport mismatch (#88480), the logic governing how models are resolved and routed to providers is currently a high-friction area.
ws Dependency Pinning (#88330): To restore Discord stability for Node 22 users.auth-profiles.json Writes (#53969): To prevent data loss during OpenAI OAuth token rotation.