manic pine
Setup:
OS: Windows 11
OpenClaw: 2026.4.26 (npm install)
Node.js: 24.14.1
Model: ollama/crab-bot-fast (Qwen)
Channels: Web UI + Telegram (@crabossbot)
Issues encountered:
Gateway wouldn't start → Runtime: unknown + ECONNREFUSED 127.0.0.1:18789. Fixed by running openclaw gateway install --force then gateway start.
Gateway boot takes ~2 minutes → caused by the acpx plugin taking ~80 seconds to initialize on every startup.
Capability: read-only stuck → the WebSocket probe keeps returning read-only even after setting gateway.auth.mode = token and tools.profile = full directly in openclaw.json. Root cause unclear.
Model not loaded in VRAM → ollama ps returned empty. Fixed by setting OLLAMA_KEEP_ALIVE=-1 as a system environment variable.
Agent repeats user messages in a loop → after cleaning corrupted sessions (doctor reported Main session transcript missing), the agent replies NO to everything regardless of input. Model works perfectly fine when tested directly via ollama run crab-bot-fast. Issue seems tied to a persistently corrupted session transcript on the OpenClaw side.
Already tried without success:
openclaw sessions cleanup --enforce --fix-missing
Archived orphan transcripts via openclaw doctor
openclaw chat --session new → TUI opens but agent still doesn't respond normally
Questions:
How do I force OpenClaw to fully ignore session history and start with a completely blank context?
Why does Capability: read-only persist despite token auth being configured?