#generation-error
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2572 issues
worked in 2026.3.13 (now i fallback to this version) >> openclaw browser --browser-profile openclaw open https://www.baidu.com 🦞 OpenClaw 2026.4.1 (da64a97) — Runs on a Raspberry Pi. Dreams of a rack in Iceland. │ ◇ GatewayClientRequestError: Error: Chrome CDP websocket for profile "openclaw" is not reachable after start.
`openclaw gateway probe` / `openclaw status --all` report `missing scope: operator.read` even though the local paired device and local operator token on disk clearly include `operator.read`.
Imported Qwen3.5-35B-A3B GGUF models fail to load when a vision projector (mmproj) file is attached. The same model loads fine for text-only (without mmproj), and loads fine with mmproj via llama.cpp's --mmproj flag. Ollama version 0.17.7 Steps to reproduce 1. Download a community Qwen 3.5 GGUF (e.g., from llmfan46/Qwen3.5-35B-A3B-heretic-v2-GGUF) and its mmproj file (Qwen3.5-35B-A3B-mmproj-BF16.gguf) 2. Create a Modelfile: FROM Qwen3.5-35B-A3B-heretic-v2-Q5_K_M.gguf FROM Qwen3.5-35B-A3B-mmproj-BF16.gguf TEMPLATE """{{ .Prompt }}""" 3. ollama create qwen3.5:test -f Modelfile → succeeds 4. ollama run qwen3.5:test → fails Also tried ADAPTER instead of second FROM — same result. Error llama_model_load: error loading model: error loading model architecture: unknown model architecture: 'qwen35moe' Expected behavior The model should load with vision support, same as it does with llama.cpp: llama-server -m Qwen3.5-35B-A3B-heretic-v2-Q5_K_M.gguf --mmproj Qwen3.5-35B-A3B-mmproj-BF16.gguf -c 4096 This works perfectly — text and vision both functional. Notes - Without mmproj, the model loads fine for text (families: ['qwen35moe']) - With mmproj, families becomes ['qwen35moe', 'clip'] and loading fails - The official qwen3.5:35b works with vision because it has native qwen35moe.vision.* tensors embedded in the main GGUF — no clip involved - PR #14517 fixed text-only loading of imported qwen35moe GGUFs but the multimodal/clip runner path was not updated for this architecture - GPU: 2x RTX 5060 16GB
When running the gateway with `gateway.bind=lan` inside Docker Desktop on macOS (Apple Silicon), the `openclaw-cli` container cannot connect to the gateway via WebSocket, making all CLI commands fail. This breaks the documented device pairing flow (`devices list` / `devices approve`).
After authenticating openai-codex/gpt-5.3-codex via OAuth (with proxy to OpenAI from mainland China network), the model can chat normally but refuses to execute any tool operations, even after modifying SOUL.md/AGENTS.md as instructed.
OpenClaw `v2026.3.13` still appears to send an extremely large context window to Ollama (around `262144` / `265k`), even when a much lower context size is configured. This looks very similar to the previously reported issue about OpenClaw forcing or propagating an oversized context window to Ollama. Although that issue was marked as fixed, I can still reproduce the behavior on the latest version.
`openclaw message thread create --channel telegram` fails with: ``` Error: Unsupported Telegram action: thread-create ```
The `LiteAgent` concatenates retrieved memory content directly into the system prompt without sanitization. If memory entries have been poisoned (e.g., via indirect prompt injection through tool outputs), an attacker can inject arbitrary instructions into the system prompt of future agent interactions. **Severity**: MEDIUM **Rule**: AGENT-010 — Unsanitized External Content in Agent Prompt **OWASP Agentic Security Index**: ASI-01 — Prompt Injection **Affected files**: - `lib/crewai/src/crewai/lite_agent.py` (lines 568-581)