Openclaw gateway stuck at Capability:read-only | Friends of the Crustacean 🦞🤝 | Page 1

valid wedge May 6, 2026, 9:46 PM

#

@Clawbot My gateway is stuck at Capability: read-only on WSL2 after
updating to OpenClaw 2026.5.4. Cron jobs run but fail because tools
like Tavily and Himalaya can't execute.

I've tried: gateway restart, doctor --repair, models auth login
--provider anthropic, configure (re-selected Claude CLI), gateway
stop + start, and sudo npm update -g openclaw.

Gateway connects fine (RPC probe: ok) but stays read-only regardless.
How do I fix this?

night capeBOT May 6, 2026, 9:46 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

valid wedge May 6, 2026, 11:40 PM

#

If anyone else had similar problem, can you please advise

rustic linden May 6, 2026, 11:56 PM

#

-I encountered similar problem just yesterday. Try this sequence

#

openclaw gateway stop
rm -rf ~/.openclaw/cache
rm -rf ~/.openclaw/tools
rm -rf ~/.openclaw/runtime
npm cache clean --force
npm install -g openclaw@latest
openclaw doctor --repair
openclaw models auth login --provider anthropic
openclaw gateway start

#

-Then verify:

#Openclaw gateway stuck at Capability:read-only