Repository navigation
Description
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After the browser.proxy invoke path was hardened to require operator.admin, openclaw nodes invoke --command browser.proxy still opens the Gateway connection with the generic node.invoke least-privilege scope (operator.write), so direct CLI browser proxy calls fail with missing scope: operator.admin before they reach the paired node.
Steps to reproduce
- Install or run OpenClaw
2026.7.1. - Pair and connect a node that advertises the
browser.proxycommand. - Ensure the Gateway allows the command, for example
gateway.nodes.allowCommands = ["browser.proxy"]. - Run a read-only browser proxy command through the generic nodes CLI:
npx -y -p openclaw@2026.7.1 openclaw nodes invoke \
--node '<paired-node-name-or-id>' \
--command browser.proxy \
--params '{"method":"GET","path":"/profiles"}' \
--json- Observe that the call fails with
missing scope: operator.admin.
Expected behavior
For node.invoke calls where command === "browser.proxy", the CLI/Gateway client scope resolver should request operator.admin, matching the gateway-side invoke requirement introduced for direct browser proxy calls.
The read-only /profiles request should then either reach the paired node and return the browser proxy result, or fail for a node/browser-specific reason after authorization. It should not fail at Gateway authorization because the CLI requested only operator.write.
Actual behavior
The call fails before node dispatch:
nodes invoke failed: missing scope: operator.adminThe paired node is connected and advertises browser.proxy, so the failure is not caused by an unavailable Mac/Chrome/node route. The same command failed with the clean npm package, not only with the locally installed package:
$ NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-issue \
npx -y -p openclaw@2026.7.1 openclaw nodes invoke \
--node '<redacted-paired-node>' \
--command browser.proxy \
--params '{"method":"GET","path":"/profiles"}' \
--json
nodes invoke failed: missing scope: operator.adminThe same direct CLI path was also checked against the beta tag:
$ npx -y -p openclaw@2026.7.2-beta.1 openclaw --version
OpenClaw 2026.7.2-beta.1 (a911e58)
$ npx -y -p openclaw@2026.7.2-beta.1 openclaw nodes invoke \
--node '<redacted-paired-node>' \
--command browser.proxy \
--params '{"method":"GET","path":"/profiles"}' \
--json
nodes invoke failed: missing scope: operator.adminOpenClaw version
OpenClaw 2026.7.1 (2d2ddc4)
Also reproduced through npx -p openclaw@2026.7.2-beta.1, which reports:
OpenClaw 2026.7.2-beta.1 (a911e58)Operating system
Ubuntu 24.04.4 LTS for the Gateway/CLI host.
The paired browser node is a connected macOS node, but the failure happens before dispatch to the node.
Install method
npm global for the installed environment.
The failing behavior was also reproduced with clean npx -p openclaw@2026.7.1 and npx -p openclaw@2026.7.2-beta.1 runs.
Model
No model involved; this is a CLI/Gateway/node authorization path.
Provider / routing chain
openclaw nodes invoke CLI -> Gateway WebSocket client -> node.invoke gateway method -> paired node command browser.proxy.
Additional provider/model setup details
Relevant node/Gateway setup:
- A paired and connected node advertises
browser.proxy. gateway.nodes.allowCommandsincludesbrowser.proxy.- No config-only scope override was found for
node.invoke browser.proxy. openclaw nodes invokedoes not expose a--scopeor--adminflag.
Logs
$ openclaw --version
OpenClaw 2026.7.1 (2d2ddc4)
$ npm view openclaw version dist-tags --json
{
"version": "2026.7.1",
"dist-tags": {
"alpha": "2026.5.19-alpha.1",
"beta": "2026.7.2-beta.1",
"latest": "2026.7.1"
}
}
$ openclaw nodes status --json
{
"nodes": [
{
"nodeId": "<redacted>",
"displayName": "<redacted>",
"remoteIp": "<redacted>",
"paired": true,
"connected": true,
"commands": [
"browser.proxy",
"system.run",
"system.run.prepare",
"system.which"
]
}
]
}
$ NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-issue \
npx -y -p openclaw@2026.7.1 openclaw nodes invoke \
--node '<redacted-paired-node>' \
--command browser.proxy \
--params '{"method":"GET","path":"/profiles"}' \
--json
nodes invoke failed: missing scope: operator.adminClean npm package source-level check:
$ node --input-type=module -e '
import { resolveLeastPrivilegeOperatorScopesForMethod as r } from "/tmp/openclaw-2026.7.1-clean/package/dist/method-scopes-DD70REaE.js";
console.log(JSON.stringify({
nodeInvokeBrowserProxy: r("node.invoke", { command: "browser.proxy" }),
nodeInvokeSystemRun: r("node.invoke", { command: "system.run" })
}, null, 2));
'
{
"nodeInvokeBrowserProxy": [
"operator.write"
],
"nodeInvokeSystemRun": [
"operator.write"
]
}Relevant clean openclaw@2026.7.1 source snippets:
// dist/method-scopes-CwW_Szsp.js
function resolveLeastPrivilegeOperatorScopesForMethod(method, params) {
if (isDynamicOperatorGatewayMethod(method)) return resolveDynamicLeastPrivilegeOperatorScopesForMethod(method, params);
const requiredScope = resolveRequiredOperatorScopeForMethod(method);
if (requiredScope) return [requiredScope];
return [];
}// dist/nodes-e1aIcs5S.js
const BROWSER_PROXY_REQUIRED_SCOPE = "operator.admin";
function clientHasOperatorAdminScope(client) {
return (Array.isArray(client?.connect?.scopes) ? client.connect.scopes : []).includes(BROWSER_PROXY_REQUIRED_SCOPE);
}
if (command === "browser.proxy" && !clientHasOperatorAdminScope(client)) {
respond(false, void 0, errorShape(ErrorCodes.INVALID_REQUEST, `missing scope: ${BROWSER_PROXY_REQUIRED_SCOPE}`));
return;
}The official browser/plugin proxy path appears to request admin explicitly:
// dist/plugin-service-DKOoYlF3.js
await browserToolDeps.callGatewayTool("node.invoke", { timeoutMs: gatewayTimeoutMs }, {
nodeId: params.nodeId,
command: "browser.proxy",
params: {
method: params.method,
path: params.path,
query: params.query,
body: params.body,
timeoutMs: proxyTimeoutMs,
profile: params.profile
},
idempotencyKey: crypto.randomUUID()
}, { scopes: ["operator.admin"] });Screenshots, recordings, and evidence
Related upstream context:
- fix(gateway): require admin scope for browser proxy invoke #85916 hardened direct
node.invoke(browser.proxy)so write-scoped callers are rejected and admin-scoped callers still dispatch. That appears to be the intended Gateway-side behavior. - fix(node-pairing): require operator.admin to approve browser.proxy nodes #104491 fixed the pairing-approval side for
browser.proxy, but this report concerns the direct invoke-time CLI/Gateway client scope resolver. - [Bug]: scope upgrade pending approval blocks all browser CLI commands #81555 and fix(browser): request admin scope for CLI control #81716 are a similar prior browser CLI scope mismatch where the CLI path was fixed to request
operator.admin. - gateway: fs.listDir node pairing can be approved without operator.admin #105936 is a similar policy-drift class for a different node command (
fs.listDir), not thisbrowser.proxynodes CLI path.
Impact and severity
Affected: users who call browser.proxy through openclaw nodes invoke or other generic node.invoke helper paths after the 2026.7.1 security hardening.
Severity: Medium to high for node-host browser workflows. The official browser/plugin path can still work when it requests operator.admin, but direct nodes CLI / helper-script workflows fail.
Frequency: Always reproduced for the direct openclaw nodes invoke --command browser.proxy path in this environment on 2026.7.1 and 2026.7.2-beta.1.
Consequence: Read-only browser proxy operations such as /profiles fail before reaching the paired node, even when the node is connected, paired, and advertises browser.proxy.
Additional information
This does not appear to be a Mac node, Chrome, pairing, or allowCommands configuration problem:
- The node is paired and connected.
- The node advertises
browser.proxy. gateway.nodes.allowCommandsalready allowsbrowser.proxy.- The Gateway correctly requires
operator.adminfor directbrowser.proxyinvoke after the hardening. - The mismatch is that the generic
node.invokeleast-privilege scope resolver still choosesoperator.writeforcommand === "browser.proxy".
Suggested fix direction:
Make the least-privilege scope resolver / CLI Gateway connection path command-aware for node.invoke, so node.invoke with command === "browser.proxy" requests operator.admin, while other generic node.invoke commands continue to use their intended lower scope. Alternatively, route the public nodes invoke browser.proxy path through the same browser proxy helper/contract that already requests operator.admin.
Last known good version in this environment: OpenClaw 2026.6.11.
First known bad version in this environment: OpenClaw 2026.7.1 (2d2ddc4).
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Jul 16, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 31, 2026, 1:56 AM ET / 05:56 UTC.
Summary
Current
mainappears to resolve the reported scope mismatch: its dynamicnode.invokescope resolver requestsoperator.adminfor commands in the shared admin-only set. I am keeping this issue open conservatively because the available evidence does not identify the exact introducing commit, timestamp, and release/main-only provenance required for animplemented_on_mainclose.Reproducibility: no. on current main from source inspection: command-aware
node.invokeresolution now selectsoperator.adminfor the shared admin-only command set. The original released-package reproduction remains credible, but this read-only review did not run a live paired-node invocation.Root-cause cluster
Relationship:
canonicalCanonical: #108951
Summary: This issue is the canonical report for the generic
node.invokeclient-scope mismatch; two linked pull requests attempted the same repair but closed unmerged.Members:
same_root_cause: fix(gateway): resolve admin scope for node.invoke admin-only commands #108961 - Its stated repair is the same command-aware resolver change forbrowser.proxyand other Gateway admin-only node commands, but it was closed unmerged.same_root_cause: fix(gateway): request admin scope for admin-only node.invoke commands #109198 - It targets the same CLI/Gateway scope mismatch and was also closed unmerged.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Ways to help us reproduce this
Next step
No repair dispatch is appropriate because current main appears to contain the fix, while the remaining task is provenance verification for a safe implemented-on-main close.
Security
None.
Review details
Best possible solution:
Identify the commit that introduced the current command-aware
node.invokeresolver, confirm whether it is shipped, and then close this issue as implemented with that provenance.Do we have a high-confidence way to reproduce the issue?
No on current main from source inspection: command-aware
node.invokeresolution now selectsoperator.adminfor the shared admin-only command set. The original released-package reproduction remains credible, but this read-only review did not run a live paired-node invocation.Is this the best way to solve the issue?
Yes for the apparent current implementation: using the shared admin-only command set makes the client connection scope match the existing Gateway gate without adding a flag, config option, or browser-specific parallel policy.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
main, but exact fix-commit and release containment provenance remains unverified; closing as implemented before that audit could misstate when users receive the repair.Codex review notes: model internal, reasoning high; reviewed against bc63c6698877.
Label changes
Label changes:
issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.clawsweeper:no-new-fix-pr: Current issue advisory state no longer selects this label.clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.clawsweeper:needs-security-review: Current issue advisory state no longer selects this label.clawsweeper:queueable-fix: Current issue advisory state no longer selects this label.clawsweeper:source-repro: Current issue advisory state no longer selects this label.clawsweeper:linked-pr-open: Current issue advisory state no longer selects this label.issue-rating: 🦞 diamond lobster: Current issue advisory state no longer selects this label.Label justifications:
P1: The latest reported release rejects a supported node browser-proxy workflow before dispatch, while current main appears repaired but release provenance is not yet confirmed.impact:security: The defect is an inconsistency between client-requested operator scope and the Gateway's admin authorization boundary.impact:auth-provider: The failure occurs in Gateway operator-scope negotiation for an authenticated RPC path.Evidence reviewed
What I checked:
src/gateway/method-scopes.tstreatsnode.invokeas a dynamic method and delegates to command-aware scope resolution; the resolver returnsoperator.adminwhencommandis in the sharedNODE_ADMIN_ONLY_INVOKE_COMMANDSset, otherwiseoperator.write. This directly coversbrowser.proxythrough the existing admin-only command contract. (src/gateway/method-scopes.ts:1305, bc63c6698877)src/gateway/method-scopes.ts:21, bc63c6698877)operator.adminboundary for directnode.invoke(browser.proxy)and merged as456c48f368cb1978433f21f295a7da7cb1faec9b; this issue reports the later client-side mismatch with that boundary. (src/gateway/server-methods/nodes.ts, 456c48f368cb)src/gateway/method-scopes.ts)v2026.7.1(2d2ddc43d0dcf71f31283d780f9fe9ff4cc04fe4), while the checked current main source contains the command-aware resolution. The exact commit that introduced the current behavior and whether it is in a later published release were not established. (2d2ddc43d0dc)Likely related people:
browser.proxynode invocation requireoperator.admin, creating the server-side contract this client resolver must match. (role: security-boundary contributor; confidence: high; commits: 456c48f368cb; files:src/gateway/server-methods/nodes.ts,src/gateway/server.node-invoke-approval-bypass.test.ts)src/infra/node-pairing-authz.ts,src/infra/node-pairing-authz.test.ts)node.invokescope-resolver approach in a closed unmerged pull request; this is relevant implementation history but not current-main ownership. (role: related resolver proposer; confidence: medium; commits: acb34db9bbfd; files:src/gateway/method-scopes.ts,src/gateway/method-scopes.test.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.vincentkoc commentedon Jul 31, 2026
Closing as fixed.
@steipete aligned the dynamic
node.invokeclient scope with the Gateway authorization boundary in #111013 (commit 62c5a8b), merged July 19, 2026. Admin-only node commands such asbrowser.proxynow requestoperator.adminbefore dispatch, matching the existing server-side gate.The fix is available in prerelease
v2026.7.2-beta.5; stablev2026.7.1predates it and remains affected.Reopen if
v2026.7.2-beta.5or newer still requests onlyoperator.writeor fails with a missing-scope error before node dispatch; include the version and redacted CLI output.