#model-save-load
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2711 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. ```
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 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.
Running `openclaw skills` produces ~75+ warning messages "[skills] Skipping skill path that resolves outside its configured root" after organizing skills in a flat directory structure.
Agents and outputs are no longer visible in chat. This happened immediately after updating to v2026.4.1. No chats are currently being displayed in the OPC chat history. Additionally, Telegram messages are only partially displayed! You never know what your agent is up to.
After updating to 2026.3.31, the dashboard at http://127.0.0.1:18789/ returns 500 Internal Server Error on every request. The gateway starts correctly (Telegram bots connect, WebSocket works, TUI works), but the HTTP handler crashes before serving any response.