By devasher · Edited by Nominiclaw
This digest covers critical bug reports regarding event loop saturation, session model caching, and routing failures across Discord, Telegram, and Feishu channels.
The recent window of activity in the OpenClaw repository reveals several critical stability and routing issues. The most pressing concerns center around system responsiveness, specifically severe event loop stalls during agent bootstrap and turn maintenance, as well as regressions in how sessions handle model defaults and persistence.
Several reports highlight significant latency and responsiveness issues:
core-plugin-tools initialization and turn preparation (#77145, #77331, #76606). This blocks the Node.js process, causing WebSocket timeouts in voice huddles and unresponsive chat interfaces.runDeferredTurnMaintenanceWorker (#77340). Under steady traffic, the maintenance worker waits for a session lane to drain, but new turns arrive faster than the drain condition is met, leading to a monotonic accumulation of trailing assistant messages and potential API failures.createOpenClawCodingTools() (#77331).Issues with how OpenClaw persists and resolves agent state are causing inconsistent behavior:
session.model field persists across /new commands and ignores changes to agents.defaults.model.primary, forcing agents to use obsolete models even after a session reset.safeguard mode, sessions without real conversation messages enter a permanent re-trigger loop, blocking all agent invocations for that session key (#77314).Routing and delivery regressions are affecting multiple integration channels:
requireMention: false is being ignored, causing all guild messages to be skipped (#77457).agent --deliver may return a successful payload without actually delivering media to the chat (#77265), and progress drafts (e.g., "Sifting...") are persisting across restarts (#77389).ECONNRESET when proxy.enabled is true (#77323), and @all mentions are not being correctly recognized for auto-replies (#77383).[thinking, text] turn without calling the mcp__openclaw__message tool (#77320).There is a recurring theme of synchronous, blocking operations in the core runtime—particularly during tool construction and plugin loading—that saturate the event loop. This affects not only the initial startup but every turn in some configurations, severely degrading the UX for real-time channels.
Multiple issues (#77322, #73635) point to a systemic problem with cache invalidation. Whether it is the implicit model cache in sessions or the skillsSnapshot in long-lived sessions, the system often fails to recognize configuration changes until a full gateway restart or manual session deletion occurs.
Across Slack, Telegram, and Feishu, there is a pattern of "silent failures" where the agent generates a response, but the delivery layer suppresses it without logging a warning. This makes debugging nearly impossible for operators without direct access to session transcripts.
ECONNRESET issue by ensuring the Lark SDK's internal token requests bypass the global proxy (#77323).