#optimization
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2913 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?
After updating from `2026.3.31` to `2026.4.1`, cron jobs that previously worked are now failing with: ``` Request timed out before a response was generated. Please try again, or increase agents.defaults.timeoutSeconds in your config. ```
When multiple model providers (e.g., Azure OpenAI and Zhipu) are configured in OpenClaw, switching to a model from a non-default provider in the UI does not correctly update the routing. The request is still sent to the default provider, resulting in a "model not allowed" error.
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.
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 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.