← Back to Blogs
GH Issues

OpenClaw Issue Digest: Critical Regressions and Runtime Stability

12:30–18:30 UTC May 10, 2026

OpenClaw Issue Digest: Critical Regressions and Runtime Stability

Open Issues

Recent activity in the OpenClaw repository reveals a series of high-impact regressions and stability issues affecting installation, runtime execution, and channel integrations. Most notably, users are reporting critical failures in the installation process on Windows/WSL and a severe crash loop triggered by the auto-compaction mechanism.

Critical Stability & Installation Issues

  • Installation Blockers: Issue #80381 reports a regression in setup.sh for v2026.5.3 and later, where Windows/WSL users encounter EACCES: permission denied when attempting to create directories in /mnt/c, effectively blocking new installations.
  • Auto-Compaction Crash Loops: A severe bug (#79224) causes the gateway to enter a crash-restart loop after successful context compaction. The old process becomes a "zombie," holding the file lock and preventing new instances from starting, resulting in total service unavailability.
  • Tarball Corruption: Issues #80355 and #80351 highlight critical packaging errors in recent versions (v2026.5.5-5.7), where bundled distributions reference content-hashed chunks missing from the tarball, leading to ERR_MODULE_NOT_FOUND and boot failures.

Model Routing & Provider Regressions

  • Codex OAuth Model Rewrite: A high-severity bug (#80363) in the update path rewrites openai-codex/gpt-* model IDs to direct openai/gpt-* IDs. For OAuth-only users, this causes primary route failures as the system attempts to use a direct API key that does not exist.
  • Gemini Stream Hangs: Users of google/gemini-2.5-flash report turns hanging for ~125 seconds when thinkingDefault is set to medium (#80349), despite the provider reporting successful streaming responses.
  • Ollama Parameter Errors: A behavior bug (#80332) sends the think parameter at the top level of Ollama requests, triggering 400 errors for non-thinking models. The parameter must be moved inside the options block.

Channel & Delivery Failures

  • Telegram Delivery Loss: Reports indicate that Telegram replies can be silently lost after polling or transport stalls (#80328). Additionally, a regex in the network error handler is too strict, causing recoverable pre-connect errors to be treated as fatal, which drops outbound messages (#80362).
  • Discord Rendering Leaks: A regression (#80356) has caused internal <<<EXTERNAL_UNTRUSTED_CONTENT>>> envelope markers to leak into both the Discord chat surface and the agent's prompt input, compromising the boundary between trusted and untrusted content.
  • Feishu Card Limits: Feishu interactive cards fail with a card table number over limit error when responses contain multiple markdown tables (#43690), with no current fallback to plain text.

Key Themes

1. Runtime and Packaging Fragility

There is a recurring theme of "broken" distributions and runtime state corruption. From missing JS chunks in npm tarballs to zombie processes during compaction, the core infrastructure is experiencing stability issues that impact the most basic operation of the gateway.

2. Tool-Call and Schema Mismatches

Several issues point to a gap between tool schemas and LLM behavior. For example, agents frequently provide both sessionKey and label for sessions_send (#41199), or include poll parameters in a standard send action for the message tool, leading to validation failures.

3. Context and Memory Management

Memory and context handling remain a primary source of friction. Issues range from the TUI connecting to the wrong session (#41168) to the lack of a a hard flush threshold in memory durability, which can lead to data loss during emergency compaction (#43432).

Action Required

Immediate Attention (High Severity)

  • #80381 (Installation): Fix the EACCES permission error in setup.sh to unblock Windows/WSL users.
  • #79224 (Runtime): Resolve the auto-compaction zombie process and lock timeout issue to prevent gateway crash loops.
  • #80355 (Packaging): Audit the build/publish pipeline to ensure all content-hashed chunks are included in the distributed tarballs.
  • #80363 (Routing): Fix the update/doctor logic to prevent the unauthorized rewriting of Codex OAuth model IDs.

Blocked or High-Friction Issues

  • #80350 (Safety): The request for a "Hard Emergency Stop" (IMST) highlights a critical architectural gap where users cannot forcibly terminate a destructive reasoning loop in real-time.
  • #80362 (Telegram): Update the network error regex to prevent silent message drops during transient socket failures.
  • #80356 (Security): Restore the sanitization logic for EXTERNAL_UNTRUSTED_CONTENT markers on the Discord surface to prevent prompt-injection risks.

References

Issues