Skip to content

[Repo Assist] fix: add operator.write scope to gateway connect handshake (closes #112)#113

Draft
github-actions[bot] wants to merge 1 commit intomasterfrom
repo-assist/fix-operator-write-scope-112-b04f34a5f5dac56b
Draft

[Repo Assist] fix: add operator.write scope to gateway connect handshake (closes #112)#113
github-actions[bot] wants to merge 1 commit intomasterfrom
repo-assist/fix-operator-write-scope-112-b04f34a5f5dac56b

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

🤖 This is an automated draft PR from Repo Assist.

Summary

The connect message sent during the WebSocket handshake declared these scopes:

["operator.admin", "operator.approvals", "operator.pairing"]
```

The `operator.write` scope was missing. The gateway requires this scope to authorise `chat.send` requests, so **all** QuickSend calls were rejected with:

```
Gateway request failed: missing scope: operator.write

This affected both the built-in QuickSend dialog (QuickSendDialog) and any custom client built against the same protocol.

Root Cause

SendConnectMessageAsync in OpenClawGatewayClient.cs (line 303) simply never included operator.write in the scopes array.

Fix

Add "operator.write" to the scopes array in the connect handshake. One-line change.

Trade-offs

None. The scope is required for an existing, intentional feature. Adding it does not broaden permissions beyond what the feature already assumes.

Test Status

dotnet test tests/OpenClaw.Shared.Tests/503 passed, 18 skipped, 0 failed

Closes #112

Generated by Repo Assist ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@cbb46ab386962aa371045839fc9998ee4e97ca64

The connect message in SendConnectMessageAsync declared scopes
["operator.admin", "operator.approvals", "operator.pairing"] but
omitted "operator.write". The gateway requires this scope for
chat.send requests, causing both the built-in QuickSend dialog
and custom clients to fail with:

  Gateway request failed: missing scope: operator.write

Closes #112

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

I developed a client to send messages to openclaw, but it consistently fails to send. Even using the demo's quick send feature also fails to work

0 participants