openclaw - 💡(How to fix) Fix Bug: macOS app browser control enabled but connected node does not advertise browser capability

Problem

The macOS app still does not advertise browser capability on a connected Mac node, even when Browser Control / browser proxy config is enabled.

This appears to be a continuing or regressed version of #5047. That issue was closed as stale after a claimed fix, but the latest release still reproduces the original symptom for us.

Current observed behavior

On ACE, the connected macOS app node is online but advertises only:

"caps": ["canvas", "location", "screen"]

and commands:

[
  "canvas.a2ui.push",
  "canvas.a2ui.pushJSONL",
  "canvas.a2ui.reset",
  "canvas.eval",
  "canvas.hide",
  "canvas.navigate",
  "canvas.present",
  "canvas.snapshot",
  "location.get",
  "screen.snapshot",
  "system.notify",
  "system.run",
  "system.which"
]

There is no browser capability and no browser.proxy command.

An older separate CLI node-host entry does show browser capability, but it is disconnected:

{
  "clientId": "node-host",
  "version": "2026.4.2",
  "connected": false,
  "caps": ["browser", "system"],
  "commands": ["browser.proxy", "system.run", "system.run.prepare", "system.which"]
}

So the browser relay is not currently available through the connected macOS app node.

Config on the Mac

The Mac config has browser enabled:

{
  "browser": { "enabled": true },
  "nodeHost": { "browserProxy": { "enabled": true } },
  "plugins": { "entries": { "browser": { "enabled": true } } }
}

Environment

• Gateway: remote VPS via Tailscale Serve (wss://clawdbot.haddock-pinecone.ts.net)
• Mac app node: ACE
• macOS app version: 2026.5.7
• macOS: 26.4.1
• Node is paired and connected
• Browser config is enabled locally

Related history

• #5047 reported this exact class of bug: Browser Control enabled but no browser cap / no relay.
• PR #39516 / commit d15b6af claimed to fix browser capability advertisement and local browser.proxy handling.
• A later comment on #5047 reported that after 2026.3.8-beta.1, the browser cap appeared but the local proxy still did not start/listen.
• #5047 was then closed by stale bot, not clearly by verified latest-release behavior.
• PR #43069 fixed a separate browser proxy JSON serialization crash.
• PR #69494 is still open for desktop browser proxy SecretRef/keychain auth, but this current symptom occurs earlier: the connected app node is not advertising browser at all.

Expected behavior

When browser control/browser proxy is enabled in the macOS app config and the app node connects:

• node caps should include browser
• node commands should include browser.proxy
• gateway browser tooling should be able to route through the connected macOS app node without requiring a separate openclaw node run process

Actual behavior

The connected macOS app node advertises canvas, location, and screen, but not browser; browser tooling cannot use that node.

Request

Please reopen/fix the macOS app browser relay path, or clarify whether the separate CLI node-host is still required. If the intended behavior changed, the app UI/config should not imply that Browser Control is active when the connected node does not advertise or serve browser capability.