Skip to content

[Bug]: nodes invoke browser.proxy requests operator.write but gateway requires operator.admin #108951

Closed

Description

@nikodim-ai

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

  1. Install or run OpenClaw 2026.7.1.
  2. Pair and connect a node that advertises the browser.proxy command.
  3. Ensure the Gateway allows the command, for example gateway.nodes.allowCommands = ["browser.proxy"].
  4. 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
  1. 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.admin

The 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.admin

The 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.admin

OpenClaw 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.allowCommands includes browser.proxy.
  • No config-only scope override was found for node.invoke browser.proxy.
  • openclaw nodes invoke does not expose a --scope or --admin flag.

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.admin

Clean 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:

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.allowCommands already allows browser.proxy.
  • The Gateway correctly requires operator.admin for direct browser.proxy invoke after the hardening.
  • The mismatch is that the generic node.invoke least-privilege scope resolver still chooses operator.write for command === "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).

Activity

  1. added
    P1High-priority user-facing bug, regression, or broken workflow.
    impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.
    impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.
    no-staleExclude from stale automation
    issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.
    clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.
    clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.
    on Jul 16, 2026
  2. clawsweeper commented on Jul 16, 2026

    @clawsweeper
    Contributor

    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 main appears to resolve the reported scope mismatch: its dynamic node.invoke scope resolver requests operator.admin for 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 an implemented_on_main close.

    Reproducibility: no. on current main from source inspection: command-aware node.invoke resolution now selects operator.admin for 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: canonical
    Canonical: #108951
    Summary: This issue is the canonical report for the generic node.invoke client-scope mismatch; two linked pull requests attempted the same repair but closed unmerged.

    Members:

    Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

    Ways to help us reproduce this

    • Add a screenshot or short recording showing the behavior.
    • Add expected vs actual behavior.
    • Include redacted logs or terminal output.

    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.invoke resolver, 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.invoke resolution now selects operator.admin for 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:

    • The observable fix is present on current 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:

    • add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
    • remove clawsweeper:no-new-fix-pr: Current issue advisory state no longer selects this label.
    • remove clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.
    • remove clawsweeper:needs-security-review: Current issue advisory state no longer selects this label.
    • remove clawsweeper:queueable-fix: Current issue advisory state no longer selects this label.
    • remove clawsweeper:source-repro: Current issue advisory state no longer selects this label.
    • remove clawsweeper:linked-pr-open: Current issue advisory state no longer selects this label.
    • remove 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:

    Likely related people:

    • LaPhilosophie: Authored the merged change that made direct browser.proxy node invocation require operator.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)
    • yetval: Authored the merged pairing-scope follow-up that aligned browser-proxy approval with the same invoke-time admin boundary. (role: adjacent authorization contributor; confidence: medium; commits: 68c18caca06c; files: src/infra/node-pairing-authz.ts, src/infra/node-pairing-authz.test.ts)
    • krissding: Proposed the same command-aware node.invoke scope-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 keeps one durable marker-backed review comment per issue or PR.
    • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
    • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
    • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
    • Maintainers can also comment @clawsweeper review to request a fresh review only.
    • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
    • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
    • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.
  3. added
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    and removed
    no-staleExclude from stale automation
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.
    clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.
    issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.
    on Jul 31, 2026
  4. self-assigned this
    on Jul 31, 2026
  5. vincentkoc commented on Jul 31, 2026

    @vincentkoc
    Member

    Closing as fixed.

    @steipete aligned the dynamic node.invoke client scope with the Gateway authorization boundary in #111013 (commit 62c5a8b), merged July 19, 2026. Admin-only node commands such as browser.proxy now request operator.admin before dispatch, matching the existing server-side gate.

    The fix is available in prerelease v2026.7.2-beta.5; stable v2026.7.1 predates it and remains affected.

    Reopen if v2026.7.2-beta.5 or newer still requests only operator.write or fails with a missing-scope error before node dispatch; include the version and redacted CLI output.

  6. locked as resolved and limited conversation to collaborators on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority user-facing bug, regression, or broken workflow.close:already-fixedclaw-marshal labelimpact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions