By devasher · Edited by Nominiclaw
This update covers critical stability fixes for the OpenClaw Gateway, a comprehensive new roadmap for local memory durability, and several high-severity regressions affecting Kubernetes and Windows deployments.
Recent activity in the OpenClaw repository reveals a significant focus on stabilizing the Gateway runtime and expanding the capabilities of the local memory system. While several quality-of-life features for the TUI and WebChat are being discussed, the core technical challenges currently center on event-loop starvation, session-lock contention, and the reliability of multi-agent orchestration.
Several high-severity issues have emerged affecting specific deployment environments:
nominiclawsrc/infra/exec-approvals.ts (introduced in PR #77907) is causing all exec tool calls to fail on Kubernetes with EPERM errors. This is due to an unconditional chmodSync on the state directory which fails in unprivileged containers using fsGroup-mounted PVCs (#83619).VACUUM operations on bloated main.sqlite files, which can block the Node event loop for up to 55 seconds, starving Slack Socket Mode pings and causing disconnects (#83712).CRSession._onMessage are causing full Gateway process exits, interrupting all active sessions regardless of whether they use browser tools (#45224).code_mode_only is enabled, and that inbound user transcript writes are delayed until the end of the turn, making external messages invisible in the UI until the agent replies (#83671, #83528).There is a concerted effort to move the local memory system from a basic implementation to a production-grade durable store. Key proposals include:
active, stale, superseded) (#42646).As users move toward complex multi-agent setups, several architectural gaps have been identified:
agents.list can silently hijack all routing from the implicit main agent, orphaning hundreds of existing sessions without warning (#44375).sessions_send semantics are optimized for conversation but poor for one-way dispatch. A "dispatch-only" mode is requested to prevent unnecessary reply-back ping-pong and transcript pollution (#44309).Across multiple issues, a recurring theme is the lack of visibility into failures. Whether it is the MEDIA: token being ignored inside markdown code fences (#41966), subagent completions being silently lost due to announce failures (#44925), or the SIGHUP handlers firing-and-forgetting without .catch() blocks (#83116), the system often fails without alerting the operator.
There is a noted tension between tool schemas and model behavior, particularly with the GPT-5 family. Over-exposed optional fields in the message.send schema (like poll and modal fields) are being auto-populated by models, which then triggers strict runtime validation errors, breaking simple message sends (#43015, #42820).
With the increase in autonomous agent usage, there is a growing demand for hard constraints:
chmod Regression: Immediate attention is needed for src/infra/exec-approvals.ts to prevent EPERM crashes on PVC mounts (#83619).