Subshell Docs

Concepts

Understand how Subshell connects your interfaces to agent processes.

Components

A server is the control plane, a node is an execution machine, and a client is your interface. Architecture shows how these components communicate.

The server serves the web interface and manages the instance database. A node runs real CLI processes in tmux, including when that execution machine is the server's own host.

Sessions

Session lifecycle separates a live process from its stored row and browser connections. An offline node isn't proof that its process stopped.

Agent state and provider credentials belong to the CLI and execution account. Subshell doesn't replace an agent's provider login or sandbox its filesystem access.

Permissions and trust

Access model explains ownership, sharing, administrators, and machine credentials. Security model explains encryption, trusted networks, plugin privileges, and accepted risks.

Platforms

Version compatibility explains why a node may connect for updates while remaining unavailable for launches.

Next steps

Use Reference for configuration values and command syntax, or Get started for setup.

Edit on GitHub

Last updated on

On this page