Skip to content

[v2026.5.3-1] [OpenClaw] Is it stable?Β #74

@github-actions

Description

@github-actions

NO πŸ”₯ β€” v2026.5.3-1

Evidence backfill changed the verdict: v2026.5.3-1 shipped with packaging breakage plus channel/runtime regressions across Docker, Discord, WhatsApp, iMessage, Telegram, Matrix, Feishu, Browser, memory, and agent runtimes. Skip it.

Stability Score: 23

Affected components

  • browser
  • discord
  • docker
  • feishu
  • imessage
  • matrix
  • memory
  • plugin-install
  • runtime
  • telegram
  • tool
  • whatsapp

Evidence

Issue Area Type Severity Penalty Reason
openclaw/openclaw#77293 plugin-install kernel 5 -5 2026.5.3-1 npm package missed install.runtime-*.js and exposed an incompatible plugin API version, breaking official plugin install/update flows.
openclaw/openclaw#80692 docker kernel 5 -5 Docker image 2026.5.3-1 shipped metadata-only channel extensions, so Discord/WhatsApp/LINE/QQBot/Feishu channels did not register.
openclaw/openclaw#77443 whatsapp channel-specific 5 -5 WhatsApp on Windows 2026.5.3-1 blocked the Node event loop after first inbound message, stalling agent model calls.
openclaw/openclaw#78419 whatsapp channel-specific 4 -4 WhatsApp health monitor restarted terminally disconnected accounts on 2026.5.3-1, causing restart loops, high heap, and gateway-wide latency.
openclaw/openclaw#77426 runtime runtime 3 -3 sessions_yield always returned No session context on MCP/claude-cli runtime path in 2026.5.3-1, breaking subagent handoff flows.
openclaw/openclaw#80819 runtime runtime 3 -3 Claude CLI live-session bridge ignored control_request can_use_tool on 2026.5.3-1, stalling sessions until timeout.
openclaw/openclaw#77718 runtime kernel 3 -3 Null agent workspace field caused a crash loop on 2026.5.3-1 and auto-restore did not repair the required field.
openclaw/openclaw#77531 runtime runtime 2 -2 CLI transcript persistence regressed on 2026.5.3-1 with Context engine legacy is not registered.
openclaw/openclaw#77566 runtime runtime 2 -2 Gemini 3.x subagent flows silently hung on 2026.5.3-1 because thoughtSignature handling was still broken across provider replay.
openclaw/openclaw#77642 runtime runtime 2 -2 5.3 regression produced duplicate answers and synthetic missing tool result in session history errors on 2026.5.3-1.
openclaw/openclaw#77649 runtime runtime 2 -2 Model-resolution and auth stages added roughly 20s of latency to every dispatch on 2026.5.3-1.
openclaw/openclaw#77673 memory runtime 2 -2 memory-lancedb npm v2026.5.3 failed to load on OpenClaw 2026.5.3-1 due to a nonexistent plugin-sdk subpath import.
openclaw/openclaw#77744 runtime runtime 2 -2 Long local llama.cpp requests timed out on 2026.5.3-1 because LLM idle timeout could not be configured correctly.
openclaw/openclaw#77416 discord channel-specific 1 -1 Discord 2026.5.3-1 channel silently skipped env-backed SecretRef token setups because dist/ sidecar layout was not resolved.
openclaw/openclaw#77503 imessage channel-specific 1 -1 iMessage polling broke after upgrading from 2026.5.2 to 2026.5.3-1: messages arrived in DB but gateway did not respond.
openclaw/openclaw#77576 telegram channel-specific 1 -1 Telegram group sessions on 2026.5.3-1 routed generated responses to webchat instead of back to Telegram.
openclaw/openclaw#77747 discord channel-specific 1 -1 Discord gateway on Windows 2026.5.3-1 remained stuck awaiting gateway readiness and never delivered inbound events.
openclaw/openclaw#78135 matrix channel-specific 1 -1 Matrix outbound m.room.message events were silently dropped on 2026.5.3-1 after agent replies were generated.
openclaw/openclaw#80120 feishu channel-specific 1 -1 Feishu channel plugin was missing after upgrading to 2026.5.3-1, so Feishu messages were not processed.
openclaw/openclaw#77730 tool tool-specific 1 -1 File-transfer nodeHostCommands were not advertised by Windows node host on 2026.5.3-1, so file tools failed against that node.
openclaw/openclaw#77733 runtime runtime 1 -1 Bare /new and /reset no longer triggered persona greetings in 2026.5.3/2026.5.3-1, regressing established reset UX.
openclaw/openclaw#77308 browser tool-specific 1 -1 Browser plugin on 2026.5.3-1 still imported a stale 2026.4.26 runtime-deps path after update, breaking browser status.
openclaw/openclaw#77350 runtime runtime 1 -1 OpenRouter DeepSeek V4 Pro requests failed with invalid reasoning_effort immediately after upgrading to 2026.5.3-1.
openclaw/openclaw#77723 memory runtime 1 -1 memory-core Dreaming cleanup still left session/trajectory residue on 2026.5.3-1.

Stats

  • Base score: 80
  • Evidence penalty: -51
  • Vote penalty: -6
  • Editorial verdict: NO

IsItStable.com β€” community-driven stability verdicts

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions