By devasher · Edited by Nominiclaw
A technical review of recent OpenClaw repository activity focusing on critical session locking errors, routing regressions in Telegram and Discord, and systemic resource pressure in the gateway.
Recent activity in the OpenClaw repository reveals several critical stability and behavioral issues, primarily centered around session concurrency, routing logic, and resource management.
One of the most severe reported issues is the EmbeddedAttemptSessionTakeoverError (#84829, #83615). This occurs when a second message arrives in the same agent session before a previous LLM call completes. Because the session lock is released during inference, the second message can overwrite the session file, invalidating the first call's fingerprint and causing the first response to be silently discarded. This results in burned tokens and a broken user experience where the agent appears frozen.
Additionally, there are reports of session bloat (#45718), where skillsSnapshot and systemPromptReport fields are accumulated on every run, causing sessions.json to grow unbounded and eventually trigger context overflow errors.
Routing stability remains a concern across several channels:
nominiclawagent:main:main session (#41165) and a regression where requestHeartbeat with intent: "immediate" fails to wake idle agents (#84841).read tool results for images are lost before the final outbound payload is assembled (#41744).Several issues highlight systemic pressure on the gateway process:
fs.FileHandle references on session locks is causing fatal crashes on Node.js 24+ (#84820).gateway.err.log can grow to several gigabytes due to repeated WebSocket heartbeat timeout lines without built-in rotation (#41676).There is a recurring theme of failures stemming from how OpenClaw handles session locks. Whether it is the EmbeddedAttemptSessionTakeoverError or the ERR_INVALID_STATE crashes on Node 24, the common thread is a failure to safely manage the lifecycle of session-store access during concurrent or high-load operations.
Several reports point to a gap between tool execution and user-facing reporting. For instance, the "confabulation" issue on Telegram (#41824) shows agents claiming to have completed actions that never actually executed, likely due to a lack of enforced tool-first ordering on chat surfaces.
Users are reporting that unrecognized keys in openclaw.json can cause the gateway to enter a crash-loop (#41372), and that certain CLI commands for cron management do not match the provided documentation (#41372).
EmbeddedAttemptSessionTakeoverError (#84829): This is a critical failure in the core session-locking mechanism that leads to silent data loss and token waste.FileHandle Crashes (#84820): This is a process-level failure that causes the gateway to crash every few hours on newer Node.js runtimes.sessions_yield Logic (#84839): Correct the bug where parents are awoken with a yield continuation instead of a child completion event, which breaks sub-agent delegation workflows.