#model-download
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2565 issues
When using a non-default profile / secondary gateway, `openclaw --profile <name> devices list` fails with: gateway connect failed: Error: gateway closed (1000): [openclaw] Failed to start CLI: Error: gateway closed (1000 normal closure): no close reason
```markdown
After updating from 2026.3.22 (also reproduced on 2026.3.23, 2026.3.24, 2026.3.31), the main agent intermittently enters a broken state: - It sends an acknowledgement like “I’ll do it now” - Then actual execution does not proceed (or appears stuck/misaligned) - Once this state appears, it does **not** recover by creating a new session - Gateway restart may temporarily recover once, but issue returns quickly - Only downgrading to an older version reliably recovers behavior This is a high-impact regression because user-visible intent/response and actual execution diverge.
After enabling sandbox mode for all my agents except the main agent, my agents are no longer able to send messages to each other. `sessions_send` does not work (times out). The non-sandbox agent (main) does not have this issue. This suggests a sandbox-specific regression in session cross-session routing.
The \message\ tool consistently returns \Error: No active WhatsApp Web listener (account: default)\ when attempting to send outbound messages, even though inbound messages are flowing normally and \openclaw channels status\ reports the WhatsApp channel as connected.
When running `openclaw gateway restart`, the Gateway service stops but fails to restart. Only a manual system restart (or computer reboot) restores the service.
When the agent sends a reply via iMessage, the sent message is picked up by `imsg watch` and fed back to the agent as a new inbound message from the remote party. This creates echo loops where the agent sees its own replies as user messages.
After upgrading from 2026.3.8 to 2026.3.11, `openclaw doctor --fix` permanently reports "5 jobs need payload kind normalization" but the fix never persists — the warning reappears on every subsequent doctor run.