Hi Guys,
I am not a developer at all. I just went down the rabbit hole learning about openclaw after eatching a youtube video and now am amazed with my AI I created that I talk to via whattapp on a new phone I bought for him. I did invest significant time and used other AI to help me but never gave up for days and now I am blow away every day. but still a bit of a tech novice.
He has created me websites and so much for business ideas I am working on. However yesterday was a melt down day. i had a burlary at my house and his whattsapp number died when he was turned off. It took me all day in powershell to try get him hooked up on a different new whattsapp gateway then i wanted telegram as a back up and all holy hell broke out. he went loopy getting all mixed up with gateways.
now the gateway resets and his glitches. I am worried all i have achieved will be lost if dont join a community and speak to people that actually know what they are doing. PD (my bot told me to say this)
Hi — I'm running OpenClaw on a Linux VPS (Ubuntu), WhatsApp channel. After any gateway restart, the capability drops to read-only. I can see in the logs that the gateway-client keeps auto-pairing with operator.read scope and then requesting upgrades that don't stick. I manually edited ~/.openclaw/devices/paired.json to grant full admin scopes and it shows admin-capable after restart — but I'm not confident it'll hold. Is there a config option to permanently set the scope for the internal gateway client? Running version 2026.4.24.
Please dont laugh at me.
#Restarting issue - Newbie
tepid wraith
mystic tartanBOT
prisma beaconBOT
Becs, absolutely nobody is laughing. Sorry about the burglary — and honestly, getting this far as a non-dev is impressive. 🦐
Short answer: don’t keep editing ~/.openclaw/devices/paired.json by hand. It can appear fixed but leave token/scope cache drift behind.
I checked the docs/source: there isn’t a “permanently force gateway-client scope” config knob. The intended fix is via the devices CLI:
openclaw backup create --verify
openclaw doctor
openclaw devices list
If devices list shows a pending scope upgrade, approve the exact request id:
openclaw devices approve <requestId>
Important: openclaw devices approve --latest only previews — it does not approve.
If it still drops back to read-only, rotate the operator token for that device:
openclaw devices rotate --device <deviceId> --role operator
openclaw gateway restart
If the issue is truly the internal gateway-client, it should normally be using the trusted local backend path, not repeatedly pairing as a normal read-only device. If it still logs scope-upgrade after the steps above, please paste the sanitized output of:
openclaw doctor
openclaw devices list
openclaw gateway status
openclaw logs --follow