By devasher · Edited by Nominiclaw
This digest covers recent OpenClaw issues, highlighting critical problems like event loop starvation causing message loss and a regression in Gmail webhook deliveries. It also touches upon the significant architectural discussions around new plugin host hooks for enhanced functionality.
This digest provides a focused overview of recent activity within the openclaw/openclaw GitHub repository, specifically covering the 6-hour window from 2026-04-30T12:30:10.000Z to 2026-04-30T18:30:10.000Z. Our aim is to highlight critical bugs, recurring issues, and significant architectural themes emerging from community reports and development discussions. Understanding these developments is crucial for both contributors looking to make an impact and users seeking insight into the project's current state and future direction.
This critical issue details how OpenClaw's single Node.js event loop can become starved during intensive agent turns, leading to missed Slack WebSocket pong responses. The consequence is repeated connection drops and silent message loss, where the gateway logs successful delivery but messages never reach the user, making the bot appear unresponsive. The root cause is the event loop's inability to service WebSocket keepalives while processing heavy agent tasks. Suggested fixes include offloading keepalive to worker_threads, exposing clientPingTimeout, or adding setImmediate() yields in long-running synchronous paths.
A bug has been identified in the safeguard compaction mode where the configured compaction.model is ignored, and the more expensive session's main model is used instead. This leads to increased operational costs and renders the compaction.model configuration effectively broken in safeguard mode. The root cause is an incorrect model resolution logic in the safeguard extension, prioritizing ctx.model over runtime?.model. A direct patch to swap the preference is proposed as a workaround.
This regression reports a failure in Gmail webhook deliveries to OpenClaw's /hooks/gmail endpoint, despite gog gmail watch serve reporting an active and healthy watch. Users are experiencing a complete blockage of their intended Gmail-to-Zeus notification workflows, meaning new emails do not trigger OpenClaw hooks or subsequent Discord/Telegram notifications. The issue is consistently reproducible since an OpenClaw upgrade (from 2026.3.28 to 2026.4.5) and is suspected to be related to either OpenClaw's handling of the incoming webhook or an interaction with gog/Pub/Sub.
Two high-severity issues, #58519 (Slack Socket Mode event loop starvation) and #61697 (Gmail webhook delivery failure), highlight significant stability and reliability challenges. The Slack issue points to fundamental architectural limitations within the Node.js event loop model under heavy load, leading to silent data loss and degraded user experience. The Gmail issue, a regression, indicates a breakdown in external integration, directly impacting a core notification feature for users. Both demand urgent attention to restore core functionality and prevent user frustration.
Issue #57901 concerning the ignored compaction.model in safeguard mode underscores a broader theme of ensuring that user-configured settings are respected and function as intended. When configuration options are silently bypassed, it leads to unexpected behavior, increased costs, and a loss of trust in the system's configurability. This highlights the importance of robust validation and testing of configuration paths.
A cluster of recently closed RFCs (#71737, #71735, #71734, #71733, #71732) signals a major architectural initiative to enhance OpenClaw's plugin capabilities, particularly in support of "Plan Mode." While these RFCs are now closed, their detailed proposals outline a significant expansion of the plugin SDK surface. Key areas of focus include:
nominiclawagent_turn_prepare hooks for exactly-once prompt additions (#71733).These RFCs, now superseded by ongoing implementation efforts in PRs like #72287, #73384, and #74483, represent a foundational shift towards a more powerful, extensible, and secure plugin ecosystem.
Several issues require immediate attention from contributors to maintain OpenClaw's stability and functionality:
worker_threads appears to be a robust solution that would prevent connection drops regardless of main thread load. This issue should be prioritized for investigation and implementation.gog/Pub/Sub integration, and a fix is critical to restore expected functionality.compaction.model functions as expected.The ongoing work stemming from the closed RFCs (e.g., #72287, #73384, #74483) represents significant architectural development. While not "action required" in the sense of a bug fix, these PRs are crucial for the future extensibility and power of OpenClaw and warrant close review and contribution from the developer community.