​

Nodes

​

What belongs where

• Advanced > Nodes: paired node status, pending pairings, capabilities, permissions, runtime clients, and raw diagnostics.
• Agent > Tools: whether a selected Agent may use node-backed tools.
• Device settings: camera, screen, microphone, location, notification, and wake-word permissions.
• Advanced > Config: raw config only when the setting does not yet have a focused page.

​

Pairing and status

fased devices list
fased devices approve <requestId>
fased devices reject <requestId>
fased nodes status
fased nodes describe --node <idOrNameOrIp>

• nodes status marks a node as paired when device pairing includes role node.
• Advanced > Nodes shows the same paired/runtime state in the browser UI.
• node.pair.* and fased nodes pending/approve/reject remain compatibility paths for clients that explicitly call the older pairing methods.

​

Node host for system.run

• Gateway host: receives messages, runs the model, routes tool calls.
• Node host: executes system.run and system.which.
• Approvals: enforced on the node host through ~/.fased/exec-approvals.json.

export FASED_GATEWAY_TOKEN="<gateway-token>"
fased node run --host <gateway-host> --port 18789 --display-name "Build Node"

fased node install --host <gateway-host> --port 18789 --display-name "Build Node"
fased node restart

# Terminal A: forward local 18790 -> gateway 127.0.0.1:18789
ssh -N -L 18790:127.0.0.1:18789 user@gateway-host

# Terminal B: connect the node through the tunnel
export FASED_GATEWAY_TOKEN="<gateway-token>"
fased node run --host 127.0.0.1 --port 18790 --display-name "Build Node"

fased devices list
fased devices approve <requestId>
fased nodes list
fased nodes rename --node <id|name|ip> --name "Build Node"

​

Exec approvals and binding

fased approvals get --node <id|name|ip>
fased approvals allowlist add --node <id|name|ip> "/usr/bin/uname"

fased config set tools.exec.host node
fased config set tools.exec.security allowlist
fased config set tools.exec.node "<id-or-name>"

/exec host=node security=allowlist node=<id-or-name>

• Node host CLI
• Exec tool
• Exec approvals

​

Common node commands

fased nodes invoke --node <idOrNameOrIp> --command canvas.eval --params '{"javaScript":"location.href"}'

• Canvas snapshot: fased nodes canvas snapshot --node <id>
• Canvas navigation: fased nodes canvas present --node <id> --target https://example.com
• Canvas eval: fased nodes canvas eval --node <id> --js "document.title"
• Camera photo: fased nodes camera snap --node <id>
• Camera clip: fased nodes camera clip --node <id> --duration 10s
• Screen record: fased nodes screen record --node <id> --duration 10s --fps 10
• Location: fased nodes location get --node <id>
• System command: fased nodes run --node <id> -- echo "hello"
• Notification: fased nodes notify --node <id> --title "Ping" --body "Gateway ready"

​

Capability notes

• canvas.*, camera.*, and screen.* usually require the node app to be foregrounded on iOS/Android.
• Camera and screen commands require OS permissions.
• Location is off by default and requires device permission.
• Android sms.send is available only on devices that support telephony and grant SMS permission.
• Screen and camera clips are duration-limited to avoid oversized payloads.
• system.run is gated by exec approvals on macOS node mode and headless node hosts.

• Camera capture
• Location command
• Media understanding
• Audio and voice notes
• Images and media
• Talk mode
• Voice wake

​

Permissions map

​

Headless node host

fased node run --host <gateway-host> --port 18789

• Pairing is still required.
• Node state lives in ~/.fased/node.json.
• Exec approvals live in ~/.fased/exec-approvals.json.
• Add --tls / --tls-fingerprint when the Gateway WebSocket uses TLS.
• For hosted gateways, use a private network path instead of public WebSocket exposure.

​

macOS node mode