Summary

Using the macOS app as a node works for pairing, canvas, and general connectivity, but browser.proxy calls crash the macOS app.

Environment

• OpenClaw macOS app: 2026.3.8-beta.1
• Build: 2026030801
• macOS: 15.7.4
• Device model: MacBookPro15,1
• Gateway/CLI observed on host: 2026.3.7

What works

• Gateway connection
• Pairing / operator approval
• Canvas present/snapshot
• Node shows as connected and paired

What fails

• browser tool routed to the macOS node
• Gateway-side failure:
  • Error: node disconnected (browser.proxy)

Reproduction

1. Install and launch the OpenClaw macOS app
2. Pair/approve the macOS app node successfully
3. Confirm the node is connected
4. Run a browser tool request against the macOS node, e.g. open/navigate using browser proxy
5. The macOS app disconnects/crashes

Observed behavior

• Canvas still works
• Browser proxy calls fail consistently
• The macOS app crashes during browser proxy handling
• Gateway logs then show the node as disconnected for browser.proxy

Crash details

Exception:

• NSInvalidArgumentException

Reason:

• Invalid type in JSON write (__SwiftValue)

Relevant stack frames:

• OpenClaw MacNodeBrowserProxy.makeRequest(...)
• MacNodeRuntime.handleBrowserProxyInvoke(...)
• NSJSONSerialization dataWithJSONObject:options:error:

Crash log excerpt

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (__SwiftValue)'
...
OpenClaw MacNodeBrowserProxy.makeRequest(...)
OpenClaw MacNodeRuntime.handleBrowserProxyInvoke(...)
NSJSONSerialization dataWithJSONObject:options:error:

Notes

• This appears isolated to browser.proxy request serialization in the macOS app
• Pairing/connectivity/canvas appear healthy after restart
• The issue reproduces on 2026.3.8-beta.1