OpenClaw v2026.5.5: Enhancements and Fixes for a Smoother Experience

Key Changes

The v2026.5.5 release of OpenClaw focuses on refining existing functionalities and addressing a wide array of issues reported by the community. This update introduces numerous fixes across different integrations, including Feishu, LINE, Telegram, Discord, and various providers like xAI and Fireworks.

Key improvements include:

• Message Routing and Session Management: Enhancements to session routing ensure that first turns and follow-ups remain within the same topic session, particularly for Feishu. LINE integration now correctly validates dmPolicy configurations to prevent silent message blocking.
• Provider Integrations: The xAI provider has been updated to stop sending unsupported reasoning effort controls to Grok Responses models, resolving Invalid reasoning effort errors. Similarly, the bundled thinking profile is now clamped to off for native Grok Responses models. Fireworks provider integrations for Kimi models have been adjusted to preserve necessary payload fields, preventing incomplete terminal replies.
• UI and Performance: The Control UI sees improvements in session management, with clearer display of compaction counts and session-level details. Performance enhancements ensure chat and channel tabs remain responsive even during slow history payloads or channel probes.
• Platform and Plugin Stability: Fixes address issues with Discord gateway heartbeat timeouts, Discord guild command routing, and Matrix approval delivery retries. Plugin diagnostics now provide more actionable warnings for users encountering issues with TypeScript packages. iOS pairing has been improved to better handle various network configurations.
• Command-Line Interface (CLI) and Tooling: The CLI and TUI have received updates for better session handling, cleaner exits, and improved diagnostic reporting. The doctor command is enhanced to better repair session-related issues.

Impact

This release addresses a significant number of user-reported issues, aiming to improve the overall stability and reliability of OpenClaw. Users can expect a more robust experience with integrations, particularly in areas like message handling, provider communication, and UI responsiveness.

Specific issues resolved include:

• #78262: Feishu message routing within topic sessions.
• #78316: LINE DM validation for dmPolicy configurations.
• #75641: Correct rendering of Telegram/Codex tool progress drafts.
• #77668: Discord gateway heartbeat ACK timeout measurement.
• #77680: Discord guild plain text command routing.
• #77785: Windows exec-approvals.json rename fallback.
• #47887: iOS pairing with LAN/Tailscale gateways and password precedence.
• #77835: Actionable warnings for missing compiled runtime output in TypeScript plugins.
• #77374: Persistence of assistant progress text in chat history.
• #76957: Correct firing of /new command and lifecycle hooks for Control UI session creation.
• #74271: Warning for shadowed OPENCLAW_GATEWAY_TOKEN environment variables.
• #77754: Avoiding duplicate fallback media posts for generated files.

Several PRs contributed to these fixes, including:

• PR #41296: Improved shutdown error visibility and added close timeouts for the gateway.
• PR #65185: Addressed iOS LAN gateway connection issues and improved password precedence.
• PR #77754: Prevented duplicate media completion fallbacks.
• PR #77907: Guarded Windows exec-approvals.json rename fallback.
• PR #77949: Ensured Codex tool progress is visible in channel drafts.
• PR #78087: Corrected Discord gateway heartbeat scheduling.
• PR #78179: Stabilized Matrix tool progress and approval delivery.

Upgrade Guide

This release primarily consists of bug fixes and does not introduce any breaking changes or require significant migration steps for most users. However, it is always recommended to review the release notes for detailed information on specific fixes that might impact your particular setup.

For users who encountered issues related to the fixes mentioned above, upgrading to v2026.5.5 should resolve those problems. As a general best practice, ensure your OpenClaw installation is kept up-to-date to benefit from the latest stability and performance improvements.