#task-chain
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2534 issues
`openclaw doctor --fix` crashes with `Config validation failed: models.providers.google.baseUrl: Invalid input: expected string, received undefined` when migrating legacy `skills.entries.nano-banana-pro` config to `models.providers.google`.
I encountered multiple issues while setting up OpenClaw on Windows using the QuickStart flow with Ollama. After completing onboarding and restarting the gateway service, the health check fails with a WebSocket error. Additionally, the embedded agent fails due to a timeout when using the default Ollama model.
When sending a file (via attachment or upload) in Lark/Feishu, if the original filename contains non-ASCII characters (e.g., Chinese, Japanese, emoji, or special symbols), the file is received with a URL-encoded filename (e.g., %E6%B5%8B%E8%AF%95.txt) instead of the original human-readable name (e.g., 测试.txt).
After upgrading to OpenClaw 2026.4.1 (da64a97), the boot-md plugin injects the same workspace file (e.g. memory/YYYY-MM-DD.md mapped as DAILY.md) 3–5× per message instead of once. Each injection appears as a separate truncation warning in the session bootstrap output. Consuming ~2% extra context budget per occurrence
Interactive Browser Tool Fails Despite Healthy Gateway (Docker / Hostinger Image) Environment Image: ghcr.io/hostinger/hvps-openclaw:latest OpenClaw version: 2026.3.8 (3caab92) Deployment: Docker (Hostinger VPS) Model: openai/gpt-5.2 OS: Linux VPS Problem Interactive browser automation fails even though both the OpenClaw gateway and browser controller are running. When prompting: open nytimes.com the agent responds: “I can’t open nytimes.com in the interactive browser because the OpenClaw gateway isn’t running on this host.” It suggests running: openclaw gateway install openclaw gateway start However this is incorrect because the gateway is already running inside the container. Verification Gateway is reachable: curl http://127.0.0.1:18789 Result: 18789_http=200 Browser controller is reachable: curl http://127.0.0.1:18791 Result: 18791_http=401 Logs [gateway] listening on ws://127.0.0.1:18789 [browser/server] Browser control listening on http://127.0.0.1:18791/ [browser/service] Browser control service ready When browser tool runs: [tools] browser failed: timed out Browser Runtime Check Chromium present: /usr/bin/chromium Playwright installed: ~/.cache/ms-playwright/chromium-* Steps Already Tried container restart openclaw doctor openclaw doctor --repair full browser state reset recreated browser profiles verified gateway + browser controller ports confirmed Playwright + Chromium installed None resolved the issue. Expected Behavior The browser tool should open the page in the managed browser. Actual Behavior Agent incorrectly reports gateway not running and falls back to HTTP fetch. Notes Other OpenClaw features work normally: Telegram bot cron jobs web fetch/search skills The issue appears limited to interactive browser tool invocation.
MiniMax image-to-image generation fails with "minimax edit does not support resolution overrides"
OpenClaw 2026.3.8 (3caab92) Setup Mac node host via SSH tunnel to local gateway Worker: 127.0.0.1:18791 → Gateway: 127.0.0.1:18789 Confirmed - tunnel works (nc -vz 127.0.0.1 18791 succeeds) - worker node service runs - worker has ~/.openclaw/identity/device.json - worker never creates ~/.openclaw/identity/device-auth.json Gateway behavior gateway logs show: device pairing auto-approved device=df72580fdf4e6ddf4a8635f50ecc2c23870a247ab1e0608feef328e4be1be34c role=node Node runtime state: Known: 1 · Paired: 0 · Connected: 1 Research Node ... unpaired · connected Device store: openclaw devices list --json { "pending": [], "paired": [ { "nodeId": "cb91b74b0afad0605fb8725ec991d86cccd24b3e059a73966a902778e19a8156" } ] } So the node reaches the runtime registry but never enters the persistent device pairing store and never writes device-auth.json. Question Why does WS node pairing auto-approve at runtime but never persist to devices pending/paired or create device-auth.json on the worker? 'Known: 1 · Paired: 0 · Connected: 1 Research Node ... unpaired · connected'
The `langchain-huggingface` README only shows: ```bash pip install langchain-huggingface ``` But `sentence-transformers` is an **optional dependency** (under `[full]` extra, requiring `>=5.2.0`). Users who follow the README and try to use `HuggingFaceEmbeddings` hit an `ImportError` at runtime with no guidance on how to fix it.
Starting a new Claude Code session in the Mac app with the **worktree** checkbox enabled fails with `Background full checkout failed: other`. The session aborts before the first turn. Unchecking the worktree box lets the session start normally. The failure is **100% reproducible** across many attempts in the same repo.