OpenClaw: Four Critical Issues Developers Need to Know

A recent scan of open issues in the OpenClaw repository (366k stars) surfaced four bugs and feature gaps that are actively affecting production deployments. Two are bugs causing silent failures, and two are missing features the community has been requesting. Here's a breakdown of each.

1. Images sent through channels never reach the model

When a user sends an image via Discord, Telegram, Feishu, or OpenWebUI, the channel adapter strips the image and passes only text to the model. Vision-capable models either respond as if no image was provided or hallucinate descriptions. The root cause is that the channel adapter interface does not propagate image URLs or base64 payloads. The fix requires extending the adapter interface to pass these image representations through. Multiple issues track this, with #23452 as the clearest summary.

2. WhatsApp and Telegram die permanently on brief DNS blip

The reconnect logic in the WhatsApp and Telegram channel adapters only handles mid-session disconnects. If a DNS failure occurs during the initial connection, the error escapes the retry loop entirely, and the channel exits with no further reconnect attempts. The gateway keeps running, but the channel is effectively dead. Users report running external watchdog scripts to restart it. See issues #2198 and #13506.

3. No way to see what's holding the session lock

The session store uses .jsonl.lock files, which get stuck regularly due to large sessions, cron load, parallel agents, or config reloads. When a lock is stuck, all models fail with session file locked (timeout 10000ms). The only recovery is manually killing the lock file or restarting the gateway. The lock file already contains pid and createdAt metadata, but there's no CLI command to surface that. A proposed openclaw locks command would read that metadata and show active waiters, giving operators actionable insight. See issues #31489 and #11950.

4. No parallel coordination between agents

The current session_spawn and send tools only support hierarchical delegation — one agent passes work down and waits. There is no way for multiple agents to collaborate on a task simultaneously or share state. Issue #43367 documents users trying to run parallel coding agents and hitting config overwrites and lock contention on top of the architecture limitation.

These four items are open for contribution and are directly impacting production setups. If you're running OpenClaw in production, check your channel adapters and session lock management — and consider contributing a fix.