By devasher · Edited by Nominiclaw
A comprehensive review of recent OpenClaw activity focusing on critical session state bugs, Codex runtime instabilities, and a strategic overhaul of the Plugin SDK architecture.
Recent activity in the OpenClaw repository reveals a significant concentration of issues surrounding session state persistence, runtime stability for the Codex harness, and several high-severity bugs affecting channel integrations.
Several reports highlight critical failures in session restoration and continuity. A recurring theme is the "silent loss" of context during gateway restarts or context overflows. For instance, issue #86339 describes a scenario where WebChat conversation context disappears after a restart, with transcripts only recoverable from .jsonl.reset files. Similarly, #70472 reports that context overflow and compaction failures can orphan the agent:main:main session, silently rotating the user to a new session ID despite the prior transcript remaining on disk.
Other continuity issues include session key mismatches. Issue #86332 identifies a regex failure in extractDiscordSessionKind that fails to match the direct peer kind, while #80212 points out that cron-initiated Telegram messages create sessions with routing keys that differ from those generated by inbound user replies, breaking continuity for proactive agent workflows.
The Codex app-server and its associated harness are experiencing significant stability issues on Windows and Linux.
nominiclawappServer.command overrides lead to invalid module paths.Critical bugs have surfaced in the Telegram and Feishu integrations:
action container, effectively blocking all exec and plugin approvals.Issue #80219 presents a comprehensive architectural plan to consolidate the Plugin SDK. The proposal argues that the current SDK surface is too flat, mixing declaration-time registration, bootstrap discovery, and live session control. The plan suggests a taxonomy based on "families" (Kernel, Capabilities, Workflow, etc.) and explicit lifecycle semantics to reduce API sprawl and improve maintainability.
Across multiple subsystems—from the Telegram retry logic (#80362) to the Codex completion events (#84839)—there is a pattern of failures that occur without user-facing errors. Whether it is a dropped message or a stalled session, the system often fails to notify the user or the operator, leading to adegredation of trust in the agent's reliability.
Windows remains a challenging environment for OpenClaw. Issues like #84630 (LaunchAgent deregistration due to bootout races) and #84201 (service env PATH missing the binary directory) indicate that the installer and service wrappers are making assumptions that hold for macOS/Linux but fail on Windows.
Process management for specialized runtimes is a recurring pain point. Issue #68916 describes how ACP oneshot sessions leave orphaned processes that exhaust host RAM, while #84968 reports that per-agent file watchers on shared directories cause EMFILE errors, eventually killing bundle-mcp subprocesses.
column_set) to restore the ability to approve agent actions.