OpenClaw Issue Digest: Session Continuity, Integration Regressions, and System Stability

Open Issues

Recent activity in the OpenClaw repository reveals a series of complex architectural gaps and regressions, primarily affecting session continuity, third-party channel integrations, and system-level stability across different hardware platforms.

Session and Routing Mismatches

Several reports highlight a breakdown in session continuity. A critical issue (#80212) describes a mismatch between outbound and inbound session keys for cron-initiated Telegram DM conversations, effectively breaking session continuity for proactive bot messages. Similarly, users of Open-WebUI are reporting session proliferation (#78091), where every message creates a new random UUID session instead of reusing a persistent one, leading to massive token waste and loss of memory continuity.

Integration Regressions

Integration stability has seen several regressions:

• Discord: Slash commands are failing to register for non-default accounts in multi-bot setups (#77359), and some users report that allowlisted users are being silently ignored while the bot owner is implicitly auto-injected into the runtime allowlist (#79043).
• Telegram: Group replies are occasionally being routed to the user's DM instead of the group chat (#79308), and plain messages in forum topics are being ignored despite requireMention: false (#79254).
• Feishu: Inbound message dispatch is failing with agent.run is undefined (#88524), and group chat replies are being silently dropped when blockStreaming is enabled (#78942).

System Stability and Performance

Hardware-specific stability remains a concern. Raspberry Pi 4 (ARM64) users are experiencing critical CPU spikes (100%+) and crash loops after upgrading to v2026.4.25+ (#79380). On Windows, users have reported hard crashes (0xC0000005) when using node-llama-cpp on Intel Alder Lake-N CPUs (#79437). Additionally, a significant regression in the Codex app-server (#86047) has caused interrupted turns and tool-execution timeouts in Nextcloud Talk sessions, forcing some operators to roll back to v2026.5.12.

Key Themes

1. The "Silent Failure" Pattern

Across multiple issues, a recurring theme is the lack of diagnostic visibility when operations fail. Whether it is the silent dropping of exec approval requests (#78738), the silent skipping of extension plugins in the gateway daemon (#78196), or the silent failure of cron announce deliveries to Telegram DMs (#79364), the system often fails without emitting a clear error or warning, making root-cause analysis difficult for operators.

2. Session and Context Fragmentation

There is a clear tension between the need for isolated execution (e.g., for crons or subagents) and the need for shared context. The request to bridge Discord voice I/O to text-channel sessions (#73699) and the need to preserve context across cross-backend model switches (#79047) underscore a demand for more fluid session transitions.

3. Security vs. Usability in Exec/Secret Paths

Several issues point to a friction point in the tools.exec and secrets paths. The undocumented Linux UID-check for system binaries (#78537) and the lack of per-binary trust (currently directory-level only, #79169) force users into using allowInsecurePath: true, which is semantically misleading for secure system paths.

Action Required

High-Severity / Blocked Issues

• #79380 (ARM64 CPU Spin): Critical. Renders the gateway unusable on Raspberry Pi 4. Requires immediate investigation into the event loop or polling logic introduced in v2026.4.25.
• #78196 (Extension Plugin Loader): High. Security plugins like ClawGuard are silently disabled in the daemon, leaving systems vulnerable to prompt injection without the operator's knowledge.
• #77979 (Pre-auth DoS): High. The lack of rate-limiting on device-signature verification allows for CPU-amplification attacks.
• #78225 (Node Allowlist Race): High. A race condition allows write-scoped callers to restore revoked admin-level exec approvals.

Contributor Attention Needed

• #88524 (Feishu Dispatch): A straightforward undefined error in the dispatch path that blocks all Feishu inbound messages.
• #88528 (Gemini Web Search): Malformed JSON responses are breaking plain searches for the Gemini provider.
• #79118 (Telnyx Auto-Response): A missing call to handleInboundResponse in the generic webhook path prevents Telnyx bots from replying to users.