search optimization

[Bug]: Gateway becomes unresponsive ~60s after startup on 2026.3.31

After upgrading from 2026.3.28 to 2026.3.31, the gateway starts successfully (binds port, loads plugins, connects WhatsApp) but becomes completely unresponsive within 30-60 seconds. The process cannot be stopped gracefully (SIGTERM times out after 30s, requires SIGKILL). Consistent across multiple restart attempts. Rolled back to 2026.3.28 — immediately stable, no issues.

why the ollama get response very slow? (QWEN3.5 35B A3B)

[Bug]: Local Ollama agent runs intermittently fail with 'fetch failed' / timeout on 2026.3.8-beta.1

On OpenClaw `2026.3.8-beta.1`, local Ollama models are callable directly via `ollama run`, but OpenClaw agent runs intermittently fail with: - `LLM request timed out` - `rawErrorPreview":"fetch failed"` This happens for both: - `qwen3.5:122b-a10b` - `gpt-oss:120b`

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

[Bug]: ERR_UNSUPPORTED_ESM_URL_SCHEME on Windows — plugin loader passes raw drive-letter paths to import()

OpenClaw version: 2026.4.5 (3e72c03) Node.js version: v22.22.2 (also reproduced on v24.14.0) OS: Windows 11 (10.0.26200) Running openclaw onboard on native Windows crashes immediately after selecting a model. The ESM loader rejects the module specifier because it receives a raw Windows path (C:\...) instead of a file:/// URL. Steps to reproduce 1. Install openclaw globally on Windows: npm install -g openclaw 2. Run openclaw onboard 3. Select Ollama as the provider 4. Select any model (e.g. ollama/gemma4:e4b) Error Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Root cause The plugin/extension loader in dist/loader-BkajlJCF.js resolves plugin paths to absolute Windows paths (e.g. C:\Users\...\extensions\openclaw-web-search) and passes them directly to jiti / dynamic import(). On Windows, ESM requires these to be file:///C:/... URLs. Relevant lines in dist/loader-BkajlJCF.js: - Line ~2526: mod = getJiti(safeSource)(safeSource); - Line ~2213: const runtimeModule = getJiti(runtimeModulePath)(runtimeModulePath); Also in dist/io-CS2J_l4V.js: - Line ~161: mod = getJiti(contractSource)(contractSource); Suggested fix Wrap paths with pathToFileURL() before passing to dynamic import: import { pathToFileURL } from 'node:url'; // Before mod = getJiti(safeSource)(safeSource); // After mod = getJiti(safeSource)(pathToFileURL(safeSource).href); Workaround Running openclaw under WSL2 avoids the issue since Linux paths don't have drive letters.

[Bug]: web_fetch blocked when DNS returns FakeIP/special-use address

web_fetch blocks when a public domain resolves to a special-use IP (FakeIP), returning "Blocked: resolves to private/internal/special-use IP address", even though the domain is public.

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

ADAPTER command fails to load mmproj (vision projection) file - 500: unable to load model

[Bug] Gateway timeout after 120ms blocks antfarm cron creation

Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running autonomously.

[Bug]: Channels (Telegram/WhatsApp) not loading in v2026.4.2 - empty table in status

Channels Empty

CUDA error on RTX 3060 Laptop 6GB with qwen3.5:4b — fixed by updating from 0.17.1 to 0.17.7

Cron: gateway restart loop should pause/defer scheduled jobs

[Bug]: Gemma4 on vLLM + PI coding agent: Validation failed for tool "edit": - path: must have required property 'path'

WhatsApp: creds.json corruption on every reconnect + overly aggressive heartbeat timeout

Two related issues with the WhatsApp channel causing constant reconnect churn on headless/VPS deployments.

[Bug]: Windows： Gateway 关闭 PowerShell 窗口后断连

在 Windows 上使用 `openclaw gateway install` 安装的计划任务，在关闭 PowerShell 窗口后 Gateway 会断连，必须重新运行 `openclaw gateway start` 才能恢复。

Slack Socket Mode: event loop starvation causes pong timeouts and silent message loss

[Bug] 流式消息组装导致 thinking/text 归类不一致（空消息或思考链冒充正文）

OpenClaw 在处理流式消息时，content 和 reasoning_content 的归类逻辑存在状态机或竞态缺陷，导致最终消息的 thinking 与 text 归类在不同运行中不一致，进而出现两种错误表现： 1. **空消息（幽灵框）**：thinking 有内容，text 缺失 2. **思考链冒充正文**：thinking 为空，text 装进了本应是 thinking 的内容

[Feature Request] Agent-initiated thread creation in Slack channels

Currently, OpenClaw agents can only **reply to existing messages** (thread replies). They cannot **initiate a new root message** in a Slack channel and use it as a thread anchor for ongoing discussion.

[Bug]: [Windows] ERR_UNSUPPORTED_ESM_URL_SCHEME when selecting sections in Control UI

**Environment** - OpenClaw version: 2026.4.5 (3e72c03) - OS: Windows 10/11 - Node.js: v22.22.2 **Description** When using the OpenClaw Control UI to configure channels, selecting "Select sections to configure" triggers an error.

[BUG] tokenizer.save_pretrained: tokenizer_class in tokenizer_config.json doesn't match the original