model compatibility

v4.1 update: bundled plugin deps not installed (Telegram/Discord broken after update)

[Bug]: 2026.3.13 local loopback regression: operator.read failures and gateway closed (1000) on CLI commands

After upgrading to OpenClaw 2026.3.13, the local loopback gateway behaves inconsistently. This is broader than the already reported status/probe `missing scope: operator.read` issue. In my case, the same gateway runtime shows: - successful local webchat/control-ui RPC for some connections - `missing scope: operator.read` for other local RPC calls - intermittent websocket handshake timeout / closed before connect - occasional failed first restart attempt before successful second start - some CLI commands failing completely with `gateway closed (1000 normal closure): no close reason` So this looks like a wider local auth/scope/session instability, not only a misleading status/probe message. Environment - OpenClaw version: 2026.3.13 - OS: Debian/Linux - Node: 22.22.1 - Gateway mode: local - Gateway bind: loopback (ws://127.0.0.1:18789) - Gateway service: systemd user service - Browser server enabled locally - Telegram channel enabled and healthy

can not run unsloth gemma-4

Bug: webchat model dropdown sends model name without provider prefix, causing 'model not allowed' error

[Bug]: exec-approvals: `ask: off` and `security: full` in exec-approvals.json not respected on Windows

Setting `ask: off` / `security: full` in exec-approvals.json has no effect on Windows; every exec call returns `exec denied: allowlist miss` even after gateway restart.

[CLI] Gateway connection fails with "gateway closed (1000)" in non-JSON mode (Potential race condition with `withProgress` spinner)

When running CLI commands like `openclaw browser status`, the connection to the local gateway consistently fails with: `Error: gateway closed (1000 normal closure): no close reason` Interestingly, the command works perfectly when the `--json` flag is added. This suggests a race condition or event-loop blockage caused by the terminal progress indica tor (spinner).

[Bug]: AnthropicException 400 - vector_store_ids: Extra inputs are not permitted

Sub-agent embedded run timeout does not release CommandLane, causing all subsequent webchat messages to be queued indefinitely

[Bug]: channels.feishu: invalid config: must NOT have additional properties

After upgrading from 3.24 to 3.28, the gateway failed to start up. openclaw doctor --fix says: **Invalid config: channels.feishu: invalid config: must NOT have additional properties** How can this issue be fixed?

a

OpenAI Codex OAuth in 2026.3.13 does not honor env proxy during code-to-token exchange

On macOS, OpenClaw 2026.3.13 completes the browser auth step for OpenAI Codex OAuth but fails at code-to-token exchange, while 2026.2.6-3 succeeds under the same proxy setup.

2026.4.5 regression: memory plugin fails — "embedding: must have required property 'embedding'" (framework config validation)

After updating to **2026.4.5**, third-party memory plugins fail to initialize with: ``` memory-lancedb-pro invalid config: embedding: must have required property 'embedding' 1 plugin(s) failed to initialize (validation: memory-lancedb-pro) ``` This does not occur on 2026.4.4 with the same config.

ollama launch claude - wrong model context window

Gateway HTTP server binds to 127.0.0.1 inside container, preventing Docker port forwarding from working

The OpenClaw gateway HTTP server binds to 127.0.0.1 inside the Docker container and is not reachable via Docker host port forwarding. Accessing the gateway from inside the container succeeds (401 Unauthorized), but requests to the host's forwarded port fail with "Connection reset by peer".

Bug: Telegram plugin fails to load after reinstall/rollback because grammY dependencies are missing

Telegram cannot start because the plugin fails to load at startup due to missing grammY-related runtime dependencies. This is not a Telegram token / webhook / network issue. The failure happens during module loading before the Telegram runtime can start.

[Feature]: Multi-provider credential pools for cross-provider failover and rotation

BlueBubbles webhook POST returns 404 despite plugin reporting 'webhook listening'

[BUG] Claude doesn't know in what directory it was opened, leading to reading files from generic path: /home/user/...

TurboQuant-MoE: SOTA 8.5x KV-cache compression with Residual Correction

openclaw doctor reports 'Telegram: not configured' despite Telegram channel working correctly

`openclaw doctor` reports `Telegram: not configured` in the channel probe section, even though the Telegram channel is fully operational.