Skip to content

Linked nodes

Each assist install is a node, with its own daemon, web server, sessions and repos. When one node links to another, its dashboard shows the other node’s sessions alongside its own, and you can start, watch and drive sessions on either node from one browser tab.

A link works in one direction. To see both nodes from either node’s dashboard, link each one to the other.

Link and unlink nodes from the Nodes page. Press Add node, enter the other node’s Web server URL, the address you open its dashboard at, and press Check. Once it shows the node’s name and version, press Link to link it. To unlink a node, pick Remove node… from its row’s ⋯ menu.

The Add node dialog on the Nodes page, with another node's web server URL enteredThe Add node dialog on the Nodes page, with another node's web server URL entered
The Add node dialog on the Nodes page, with another node's web server URL entered

A node’s name labels its sessions on every node that links to it. It defaults to the hostname, with -wsl added under WSL. To change it:

Terminal window
assist config set sessions.nodeName laptop

A link must use the peer’s node name, so if you rename a node, re-link it on every node that links to it.

Once a link exists, the toolbar shows a node picker. The node you pick is the one the toolbar’s PR and run menus, the history list, and views like Backlog and Config work against. Each entry shows the link’s state, the peer’s version and a behind chip when that node runs an older assist.

The node picker listing this node and a linked one, with a session from the linked node in the sidebarThe node picker listing this node and a linked one, with a session from the linked node in the sidebar
The node picker listing this node and a linked one, with a session from the linked node in the sidebar

The New session dialog’s Node choice picks where the session runs. Cards for sessions on a linked node carry a badge naming that node, such as laptop. To move a backlog run that started on the wrong node, use Transfer on its top bar.

The Transfer menu on a backlog run's top bar, listing a linked node to move the run toThe Transfer menu on a backlog run's top bar, listing a linked node to move the run to
The Transfer menu on a backlog run's top bar, listing a linked node to move the run to

A transfer that is waiting its turn shows a banner on the session with Cancel transfer. One that fails shows the error with Retry and Dismiss.

With a linked node picked, the dashboard menu’s Restart and Update assist items act on that node, and its row on the Nodes page has the same actions.

To link nodes over Tailscale, turn on MagicDNS and HTTPS certificates in your tailnet’s admin console. Each web server then makes its port available on the tailnet when it starts. To keep a node off the tailnet:

Terminal window
assist config set sessions.tailscaleServe false

When two linked nodes’ assist versions are too far apart to talk to each other, the link stays blocked until you update the older one. To connect anyway, set warn. To skip the check entirely, set off:

Terminal window
assist config set sessions.linkVersionCheck warn