Subshell Docs

Version compatibility

Check compatibility between a control plane and its execution nodes.

Component versions

The server, node, server desktop app, and client desktop app have independent release versions. GitHub release prefixes identify the installed component:

PrefixComponent
cli-server-vStandalone control plane.
cli-node-vStandalone node daemon.
desktop-server-vServer desktop app and bundled server.
desktop-client-vClient desktop app and bundled node.

A desktop update must ship the CLI it wraps. Installing a newer standalone binary doesn't change the contents of an older downloaded desktop bundle.

Node compatibility

The server checks that each node meets its minimum release version and uses the same protocol version. A recent node release still needs to pass the protocol check.

A node with an incompatible version can stay connected so you can update it. Until then, you can't launch subshells or use its other management controls.

Choose an update

Check the dashboard's update page or use the installed CLI to see which release your server supports. The server reports its requirements, so you don't need to keep a separate version list.

For air-gapped operation, stage compatible signed release artifacts and use local-file workflows as documented. An empty release source disables automatic fetching; it doesn't remove protocol checks.

See also

Node updates, Update the server, and Node protocol.

Edit on GitHub

Last updated on

On this page