snth node

Give your synth
a real computer.

An execution node is your own Mac or Linux machine doing the work your synth plans: agent runs with Codex, Claude Code, Kimi, or ZCode (GLM), and persistent terminals — with the access level you choose, over outbound connections only.

Install with one command

$ curl -fsSL https://github.com/snth-ai/work-node-releases/releases/latest/download/install-work-node.sh | sh

macOS 13+ (Apple silicon & Intel) and Linux. Free during the research preview.

Three steps, then it just runs.

The installer talks you through everything in the terminal. No account details are typed into the browser, and nothing is downloaded without a checksum.

Run the command
It downloads the node for your platform, verifies the published SHA‑256 checksum, and brings its own pinned toolchain — Node.js runtime and coding-agent adapters — before registering a background service. No inbound port is ever opened.
Paste your connect code
The installer asks for a one-time code from your portal: Work → Settings → Nodes → Add execution node — then which coding agents run here, and how much of the machine they may use. The code expires in 15 minutes, works once, and is decoded only on this machine.
Watch it turn Online
Back in the portal, the node goes from “Waiting for first heartbeat” to Online on its own. From then on it picks up runs and terminals for your account — and nothing else.

What runs here.

The node executes what you or your synth prepare in Work — every attempt is bounded, recorded, and reviewable in the portal.

Agent runs

A run arrives as a frozen context pack — brief, documents, file references, permissions. The node executes it through Codex, Claude Code, Kimi, or ZCode and streams structured events and artifacts back to the portal.

Persistent terminals

A real shell in your browser, backed by tmux on this machine. Close the laptop, reconnect later — the session survives, byte for byte.

Scoped tools

When a run is granted a connected app or repository, the node brokers exactly that grant — Codex never sees your provider credentials or account tokens.

Built to be trusted with your machine.

The node is designed so that the most paranoid reading of it is the correct one.

Outbound only The node makes HTTPS connections to snth — never the other way around. It opens no listening port, and your browser never connects to your machine.
You choose the access level Full access lets runs use this account like you do — the right choice when the node should act as your second pair of hands. Workspace only confines every run to the folder you picked, enforced by an operating-system sandbox (Seatbelt on macOS, Bubblewrap on Linux); the installer refuses that choice on a machine where it cannot be enforced. Each coding agent also applies its own boundaries on top.
Verified downloads Every binary is fetched from the public release channel and verified against its published SHA‑256 checksum before it is installed or upgraded.
Secrets stay where they belong The node credential lives in a private file on this machine. The coding agent receives a minimal environment: no snth credentials, no provider secrets. Repository access uses short-lived, run-scoped tokens that are redacted from output.
One-time connect code The code you paste is single-use and expires in 15 minutes. It is exchanged for a node-bound credential and then deleted.
Yours to remove Stopping the service stops all of it. Uninstalling removes the binary, the runtime, and the credential — and the portal shows the node offline immediately.

Requirements.

If the command runs, you are probably fine. For the record:

macOS 13 or newerApple silicon or Intel
Linuxx86-64 or ARM64, with systemd user services
Nothing else to installthe node brings its own checksum-verified Node.js runtime, agent adapters, and tmux — no Homebrew or package manager required
Workspace-only modeoptional; needs Seatbelt (built into macOS) or Bubblewrap on Linux
Agent sign-ineach coding agent (Codex, Claude Code, Kimi, ZCode) signs in locally on this machine; credentials never leave it — Kimi and ZCode additionally need their own CLI or app installed
Networkoutbound HTTPS to snth — no port forwarding, no VPN required

Upgrade, inspect, remove.

The node is a normal user service on your machine — no hidden daemons, no root.

Upgrade in place

$ curl -fsSL https://github.com/snth-ai/work-node-releases/releases/latest/download/install-work-node.sh | sh -s -- --upgrade

Logs & status — macOS

tail -f ~/.local/state/snth/work-node/work-node.log
launchctl print gui/$(id -u)/ai.snth.work-node

Logs & status — Linux

journalctl --user -u snth-work-node -f
systemctl --user status snth-work-node

Uninstall — macOS

launchctl bootout gui/$(id -u)/ai.snth.work-node
rm ~/Library/LaunchAgents/ai.snth.work-node.plist
rm -rf ~/.local/share/snth-work-node \
  ~/.local/state/snth/work-node \
  ~/.local/bin/snth-work-node

Then remove the node in the portal under Work → Settings → Nodes.

Uninstall — Linux

systemctl --user disable --now snth-work-node
rm ~/.config/systemd/user/snth-work-node.service
rm -rf ~/.local/share/snth-work-node \
  ~/.local/state/snth/work-node \
  ~/.local/bin/snth-work-node