OpenClaw Issue Digest: Runtime Parity, UI Regressions, and Memory Management

Open Issues

The current development cycle is heavily focused on the transition to Codex as the default runtime. A major effort is underway to establish a "Codex-vs-Pi" runtime parity QA harness (#80171) to ensure that tool surfaces, auth profiles, and plugin lifecycles remain consistent across runtimes. This includes a multi-phase rollout featuring a drift classifier to detect structural or tool-call differences and a token-efficiency report to prevent cost regressions during the flip.

On the user-facing side, several regressions have been reported regarding the v2 Control UI. Users are experiencing "sluggish" behavior where the dashboard becomes progressively stuck after being open for a while (#46598), alongside specific usability failures such as unreadable tool bubbles (#45649), obscure session views (#45711), and a chat input that requires double-pressing enter for certain commands (#45569).

Memory and session management also remain a point of contention. Reports indicate that sessions are accumulating skillsSnapshot and systemPromptReport fields on every run, leading to unbounded growth of sessions.json (#45718). Additionally, there is a reported gap in the daily-reset mechanism where archived session history becomes invisible in the UI, prompting requests for a restoration utility script (#45003).

Key Themes

Runtime Parity and Stability

With the shift toward Codex, the community is identifying gaps in how different runtimes handle tool calls and auth. For instance, there is a reported issue where auth.order is ignored for the GitHub Copilot provider, causing the first profile in the list to always win regardless of configuration (#46031). There is also a critical concern regarding "silent stalls" in Codex ACP runs when the gateway child environment lacks proper proxy access (#44810).

Channel-Specific Routing and Delivery

Several issues highlight inconsistencies in how messages are routed across different channels:

• Telegram: Reports of messages being silently dropped due to update offset race conditions (#44930) and failures in delivering MP4 files via message send --media (#80389).
• Discord: A reported preflight bug where mention-gating is too permissive, allowing messages to be routed to the wrong agent when other agents or roles are mentioned in the text (#44502).
• Feishu: Issues with multi-agent routing where all messages are routed to a single agent regardless of the binding configuration (#45158).

Security and Isolation

Security remains a priority, with a high-profile request to implement OS-level sandboxing for exec() calls (using bwrap on Linux and sandbox-exec on macOS) to prevent agents from executing dangerous commands with full user privileges (#58730). Similarly, there is a request to mount skill directories as read-only in sandbox containers to prevent agents from modifying their own instruction sets (#17931).

Action Required

High Severity / Blockers

• Runtime Parity Harness (#80171): This is the primary architectural goal to prevent regressions during the Codex transition. Immediate attention is needed for Phase 1 (Runtime Axis) to unblock subsequent tool-fixture and token-efficiency work.
• Control UI Performance (#46598): The progressive sluggishness of the dashboard is a significant UX blocker for operators managing long-running gateways.
• Security Gaps (#58730, #17931): The lack of exec() isolation and writable skill directories represent a fundamental security risk for autonomous agents.

Blocked or Urgent Fixes

• Telegram Webhook Hangs (#80454): Gateway restarts are currently blocked for 30+ minutes by a Telegram deleteWebhook retry loop, which is a critical failure in the boot sequence.
• Session Bloat (#45718): The unbounded growth of sessions.json can lead to context overflow errors and requires a systemic fix to how snapshots are persisted.