`clawdbot node`

Run a headless node host that connects to the Gateway bridge and exposes system.run / system.which on this machine.

Why use a node host?

Use a node host when you want agents to run commands on other machines in your network without installing a full macOS companion app there.

Common use cases:

Run commands on remote Linux/Windows boxes (build servers, lab machines, NAS).
Keep exec sandboxed on the gateway, but delegate approved runs to other hosts.
Provide a lightweight, headless execution target for automation or CI nodes.

Execution is still guarded by exec approvals and per‑agent allowlists on the node host, so you can keep command access scoped and explicit.

Start (foreground)

clawdbot node start --host <gateway-host> --port 18790

Options:

--host <host>: Gateway bridge host (default: 127.0.0.1)
--port <port>: Gateway bridge port (default: 18790)
--tls: Use TLS for the bridge connection
--tls-fingerprint <sha256>: Pin the bridge certificate fingerprint
--node-id <id>: Override node id (clears pairing token)
--display-name <name>: Override the node display name

Daemon (background service)

Install a headless node host as a user service.

clawdbot node daemon install --host <gateway-host> --port 18790
# or
clawdbot service node install --host <gateway-host> --port 18790

Options:

--host <host>: Gateway bridge host (default: 127.0.0.1)
--port <port>: Gateway bridge port (default: 18790)
--tls: Use TLS for the bridge connection
--tls-fingerprint <sha256>: Pin the bridge certificate fingerprint
--node-id <id>: Override node id (clears pairing token)
--display-name <name>: Override the node display name
--runtime <runtime>: Service runtime (node or bun)
--force: Reinstall/overwrite if already installed

Manage the service:

clawdbot node status
clawdbot service node status
clawdbot node daemon status
clawdbot node daemon start
clawdbot node daemon stop
clawdbot node daemon restart
clawdbot node daemon uninstall

Pairing

The first connection creates a pending node pair request on the Gateway. Approve it via:

clawdbot nodes pending
clawdbot nodes approve <requestId>

The node host stores its node id + token in ~/.clawdbot/node.json.

Exec approvals

system.run is gated by local exec approvals:

~/.clawdbot/exec-approvals.json
Exec approvals
clawdbot approvals --node <id|name|ip> (edit from the Gateway)

2.7 KiB Raw Blame History Unescape Escape

clawdbot node