#mixed-precision
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2585 issues
2026.3.14, tools.profile (coding) allowlist contains unknown entries (apply_patch, image). These entries are shipped core tools but unavailable in the current runtime/provider/model/config. What matter? Why?
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
The Matrix plugin fails to load in Docker (`openclaw:local` or built images) with the persistent error: [matrix] [default] channel exited: Cannot find module '@vector -im/matrix-bot-sdk' Require stack:/app/dist/matrix-ZSlmDGn7.js Even after: - Deleting `/app/extensions/matrix`, `/app/dist/matrix-*.js`, and `/home/node/.openclaw/extensions/matrix` - Running `openclaw plugins install @openclaw/matrix` - Running `npm install --omit=dev` in both locations - Multiple `--no-cache` rebuilds using a custom Dockerfile with `OPENCLAW_EXTENSIONS=matrix` - Cleaning the config with `openclaw doctor --fix` and manual resets The loader keeps hitting the incomplete bundled version shipped in the base image. The user-installed copy never fully takes precedence, and the runtime is missing `@vector-im/matrix-bot-sdk` (and sometimes other shared modules). ai helped me write this report after a day of trying to get matrix plugin installed and working properly in openclaw. would be nice to use a real messenging protocol and element instead of the channels of telegram and signal.
The Control UI (webchat) crashes and becomes unresponsive after a WebSocket reconnect. The gateway logs show repeated `missing scope: operator.read` errors when the frontend attempts to call `config.get` and other operator-level APIs.
The onboard wizard stores "${MIMO_API_KEY}" (env var reference) in config instead of the resolved value. Webchat resolves it correctly at runtime but Feishu channel passes the literal string to the model API, causing 401 errors.
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.
root@YANHUA:~/.openclaw# openclaw browser extension install Config was last written by a newer OpenClaw (2026.3.31); current version is 2026.3.24. error: too many arguments for 'browser'. Expected 0 arguments but got 2. root@YANHUA:~/.openclaw# openclaw browser extension path Config was last written by a newer OpenClaw (2026.3.31); current version is 2026.3.24. error: too many arguments for 'browser'. Expected 0 arguments but got 2. root@YANHUA:~/.openclaw# I can control browser via Managed Browser or Remote CDP, but when installing the browser extension, it thows out the error message above.
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.