#parallel-task
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2562 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.
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.
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"
`openai-codex` appears to enter the generic OpenAI websocket transport path on current `main`, but the websocket connection target is still the generic OpenAI Responses websocket endpoint. In an isolated smoke test on merged `upstream/main`, this causes the websocket attempt to fail with HTTP 500 and fall back to HTTP transport. The chat/tool flow still succeeds after fallback, so this is not a total functional failure. The issue is that the `openai-codex` provider seems to be treated as websocket-eligible without clear evidence that the generic OpenAI websocket endpoint is the correct transport target for the Codex OAuth path.
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.
Two related issues with the WhatsApp channel causing constant reconnect churn on headless/VPS deployments.