fix: use openclaw-control-ui client identity for gateway scope bypass#22
Merged
Conversation
The upgraded gateway clears scopes for non-control-ui clients without device identity. ClawChat was identifying as 'cli' which meant the dangerouslyDisableDeviceAuth bypass didn't apply, causing 'missing scope: operator.read/write' errors on every request.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
After upgrading the OpenClaw gateway, ClawChat connections fail with
missing scope: operator.read/operator.writeerrors on every request.Cause
The new gateway version enforces scope-based auth and clears scopes for clients without device identity — unless the client identifies as
openclaw-control-ui(which gets thedangerouslyDisableDeviceAuthbypass). ClawChat was identifying ascli, so the bypass never applied.Fix
Change
client.idfromclitoopenclaw-control-uiandclient.modefromclitowebchatin the connect handshake (4 lines ingateway-client.ts).