#tokenizer-error
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2544 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.
When a session context becomes large enough to trigger compaction, and that compaction process times out, the agent enters a silent failure loop. Each timeout (~10 min) triggers a delivery retry that resends the same message to the user repeatedly — with no recovery, no fallback, and no way for the session to self-resolve.
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.