Plugins
Manage the plugins available to your Subshell instance.
Before you start
Sign in to the dashboard as an administrator. Plugins run in the server's process with all of its privileges.
Plugin trust
Installing a plugin runs third-party code in the process holding the node signing keys. A malicious plugin can affect the instance and its enrolled nodes.
Manage the set
- In the server dashboard's sidebar, open Settings → Server Settings → Plugins.
- Review installed harness, terminal, and network plugins.
- Install a trusted package specification when adding a third-party plugin.
- Enable or disable it for the instance.
- Review the impact before uninstalling.
The server stores plugins and controls which ones are enabled for all nodes. You don't need to install or enable them separately on each node.
Enabling a harness doesn't install its CLI on each node. Availability combines the instance's plugin state with binary detection on the target machine.
Built-ins and uninstalling
Built-in plugins are available without a download and are installed on first startup. If you uninstall them, restarting the server won't add them back.
The host validates plugin capability declarations when loading code. Network plugins have a different interface from harness plugins and don't appear in agent launch pickers.
Next steps
See Install an agent CLI, Networking, and Plugin API.
Edit on GitHubLast updated on
