ISR setup

Ollama API error 400: {"error":"registry.ollama.ai/library/Qwen3.5:0.8b does not support tools"}

Browser cannot attach/use healthy local Brave CDP on hardened Debian 13 VPS

On a hardened Debian 13 VPS, OpenClaw browser automation fails even though Brave is running headless, exposes a valid CDP endpoint on localhost, and returns a valid `webSocketDebuggerUrl`. OpenClaw reports the browser profile as **not running**, returns **no tabs**, and `browser open` fails with **PortInUseError** instead of attaching to the existing CDP browser. This appears to be an OpenClaw Linux/VPS browser attach/runtime issue, not a missing-browser or broken-CDP issue.

Claude Code fails with non-Anthropic models via LiteLLM Proxy (Unknown parameter: output_config)

RFC: Detecting silent behavioral drift in agents across session boundaries

AMD RDNA4 (gfx1201 / RX 9060 XT) not detected – Ollama falls back to CPU (0 VRAM)

[BUG] claude.ai Gmail MCP auth flow broken in Claude Code CLI on Linux — Enter key does nothing after browser auth

bug(agents): OpenAI WS replay drops message-level phase when block has explicit textSignature — commentary leaks on history replay

Verbose mode not properly registered in app launch code

[Installation]: PyPI release blocks installation on enterprise systems: xgrammar==0.1.29 blocked by security scanners (CVE-2026-25048)

[Bug]: npm global install of 2026.4.x silently omits channel plugin dependencies, causing cascading MODULE_NOT_FOUND on every CLI command

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.

[Feature]: OpenCode Zen/Go catalog / modern-model policy follow-up

The newly release minimax-m2.7 is added to both opencode zen and opencode go it is not added in the openclaw models list

[Bug]: The Gateway daemon of OpenClaw crashes on the laptop when the device switches from being powered by the AC adapter to battery power.

CPU Intel(R) Core(TM) i7-4900MQ CPU @ 2.80GHz 2.80 GHz RAM 32.0 GB (31.7 GB 可用) 238 GB SSD SAMSUNG MZ7LN256HCHP-000L7, 1.82 TB HDD ST2000LM015-2E8174 NVIDIA Quadro K3100M (4 GB), Intel(R) HD Graphics 4600 (113 MB) Windows 10 专业版 VERSION:22H2 OS Internal version 19045.6466 I normally use the laptop with the AC power adapter plugged in, and OpenClaw runs completely fine. But as soon as I unplug the adapter and switch to battery power, the OpenClaw Gateway daemon crashes every single time — the failure rate is 100%.

[BUG] Claude Pro subscription paid but account shows Free Plan — Invoice LF31MC1L-0002

[Bug]: Bug Report: OpenClaw 2026.3.11 breaks all Tool Execution for `moonshotai/kimi-k2.5` via `openai-completions`

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.).

[Bug/UX] Control UI loses gateway token after container rebuild

V2 model runner crashes on Qwen3.5 mixed attention (linear + full)

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`.

[BUG]If result_as_answer=true is set, then irrespective of tool's failure or success ,tool output which essentially is error returned will become final answer of agent

If a tool with result_as_answer=True is given to agent, Agent ignores the success of tool and make the tool output it's own, which shouldn't happen. result_as_answer=True should work for only successful tool calls ,This essentially removing the capability of agent reflecting on it's output

[Bug]: Model "openai-codex/gpt-5.4-mini" not found. Fell back to "openai-codex/gpt-5.4".

it is not picking gpt-5.4-mini from openai-codex

[openclaw-lark] Owner-only restriction on OAuth and User API prevents multi-user deployment

The `openclaw-lark` plugin restricts Feishu (Lark) User Access Token (UAT) operations to only the **App Owner**. This means in a multi-user deployment where the bot serves an entire organization, non-owner employees cannot: 1. **Initiate OAuth authorization** — `oauth.js` checks `assertOwnerAccessStrict()` and returns `permission_denied` for non-owners 2. **Call any Feishu user API** — `tool-client.js` calls `assertOwnerAccessStrict()` in `invokeAsUser()`, blocking all UAT-based tools (calendar, tasks, bitable, IM, etc.) for non-owner users

MiniMax M2.7 Cloud model request