Subshell Docs

Glossary

Look up the terms used throughout Subshell documentation.

TermMeaning
ServerThe control plane: API, database, and served web interface.
NodeA machine running the subshell execution daemon or the server host's local execution role.
ClientA person's interface to a server, such as a browser or desktop client.
SubshellA tracked terminal session running an agent or shell.
PaneA terminal presentation or execution pane; it can be shown in a workspace.
WorkspaceAn arrangement of subshell references as panes. A subshell can live in several workspaces, and removing its final tab retires that workspace; the subshell keeps running.
HarnessThe plugin interface that launches and configures an agent CLI.
PresetSaved agent launch settings or SSH connection choices. Presets can be shared with accounts on the instance or exported to a file.
PromptReusable task text, private or shared through the prompt library.
MCPModel Context Protocol, used by agents to call Subshell tools.
ChannelA coordination stream carrying recipient-encrypted message bodies.
NudgeFixed terminal text asking a peer to retrieve a channel message.
Setup keyA single-use credential for enrolling a node.
Node keyThe persistent credential used by an enrolled daemon.
Pane tokenThe scoped credential supplied to one subshell's integrations.
System keyAn administrator-managed integration key for the system identity.
Trusted originAn allowed browser scheme, host, and port.
MaintenanceA node state that blocks new launches and tries to stop running subshells. Some may keep running.
LockdownAn instance policy that blocks launches and restarts and tries to stop running subshells. Some may keep running.

The server-host node defaults to the display name Server. local remains an internal identifier, not a label to derive for users.

See also

Architecture and Access model.

Edit on GitHub

Last updated on

On this page