← Back to Blogs
GH Issues

OpenClaw Issue Digest: Memory Pipeline Stability and Execution Guardrails

18:30–00:30 UTC May 13, 2026

OpenClaw Issue Digest: Memory Pipeline Stability and Execution Guardrails

Open Issues

Recent activity in the OpenClaw repository reveals a significant volume of behavioral bugs and architectural gaps, particularly concerning the memory-core plugin, the exec tool's stability across platforms, and provider-specific regressions for Claude CLI and Gemini.

Memory and Dreaming Pipeline

Several issues highlight instability in the "Dreaming" pipeline. Users report that the light-phase work summary repeats verbatim across cycles (#72096) and that the dreaming cron reports success while writing no artifacts (#72546). Furthermore, the dreaming corpus is frequently polluted by cron-triggered noise (#68449), and the light-sleep sort order prioritizes recency over actual recall counts, effectively hiding meaningful data (#71976).

Execution Tool and Sandbox Stability

Stability issues with the exec tool are prevalent across different operating systems. On macOS, users are experiencing intermittent SIGKILL events during broad diagnostic commands (#72240), while Windows users report spawn EPERM errors that block all commands (#71717). In sandboxed environments, there are reports of uv_interface_addresses errors causing gateway disconnects (#71721) and a failure to propagate sandbox.docker.env variables to subagents (#69327).

Provider and Auth Regressions

Provider-specific issues are surfacing, particularly with the claude-cli backend. Reports indicate that sessions are reset on every turn in group channels due to extraSystemPromptHash drift (#69118) and that the backend skips context engine maintenance, breaking LCM persistence (#81558). Gemini users are reporting intermittent 0-token stalls in isolated subagent sessions (#80714) and 404 errors when spawning sub-agents with specific preview models (#71932).

UI and Channel Integration

User experience issues in the Control UI include duplicate assistant replies (#71992, #72892) and a "flash" of the credentials gate during tab re-focus (#72500). On the channel side, the Telegram outbound path is leaking reaction directives as literal text (#71140), and the Feishu bot is stripping its own mentions, leading to NO_REPLY in multi-bot groups (#72504).

Key Themes

1. The "Silent Failure" Pattern

Across multiple subsystems, OpenClaw is exhibiting a pattern of silent failures where the system reports ok or success while the actual output is missing or degraded. This is seen in the Dreaming cron (#72546), the claude-cli persistence gap (#81558), and the gateway's handling of empty fallback chains (#81459).

2. Resource and Process Management

There is a recurring theme of process lifecycle mismanagement. This includes the agent/cli-backend watchdog killing sessions that are correctly idle during Monitor tasks (#71803), and openclaw-agent processes ignoring SIGTERM under cron, leading to RAM exhaustion (#71710).

3. Context and Session Continuity

Session "amnesia" is a critical pain point. Whether caused by missing-transcript races in Telegram DMs (#77974) or system-prompt hash drift in group channels (#69118), the inability to maintain conversational state across turns is significantly degrading the agentic experience.

Action Required

High Severity / Critical

  • Security: Secret Redaction in exec (#72111): The exec tool returns raw stdout/stderr to agents without redacting secrets, posing a high internal exposure risk.
  • Security: Pairing Bypass (#72418): A vulnerability allows loopback clients to self-declare GATEWAY_CLIENT identity and bypass device pairing.
  • Stability: Windows Hard Crashes (#71699): The gateway is experiencing STATUS_STACK_BUFFER_OVERRUN crashes during Mattermost streaming replies.

Blocked or Immediate Attention

  • Claude CLI Persistence (#81558): The lack of runContextEngineMaintenance in the CLI path effectively disables LCM for a large segment of users.
  • Dreaming Artifacts (#72546): The failure to write artifacts despite successful cron runs renders the dreaming feature invisible to users.
  • Bedrock Auth (#72031): The image tool is currently broken for Bedrock users due to an unconditional requireApiKey call that ignores aws-sdk mode.

References

Issues