#request-error
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2619 issues
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
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).
The `openai-codex` provider (targeting `chatgpt.com/backend-api/codex/responses`) does not cap the `instructions` field before sending. When workspace bootstrap files + system prompt + tool schemas exceed ~32 KiB, the API returns `{"detail":"Bad Request"}` (400). This makes GPT-5.4 unusable for agents with larger workspaces.
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?
After upgrading from a previous npm global install to OpenClaw 2026.4.x (tested on 2026.4.3 and 2026.4.5), every CLI command fails with `Cannot find module` for channel plugin dependencies (`@slack/logger`, `@buape/carbon`, `@larksuiteoapi/node-sdk`, `grammy`), because the `packageManager: pnpm` declaration causes npm to silently drop these packages during global install hoisting.
The newly release minimax-m2.7 is added to both opencode zen and opencode go it is not added in the openclaw models list
When using moonshotai/kimi-k2.5 (via NVIDIA NIM, api: openai-completions) as the primary agent in OpenClaw 2026.3.11, the agent completely fails to parse and execute any tools (including read, exec, web_search, etc.).
When enabling `VLLM_USE_V2_MODEL_RUNNER=1` with Qwen3.5 models (`Qwen3_5ForConditionalGeneration` / `Qwen3_5ForCausalLM`), the engine crashes during KV cache initialization with an `AssertionError` in `_reshape_kv_cache`.
it is not picking gpt-5.4-mini from openai-codex