Terminal
Shells, machine selection, terminal tabs, file uploads and connection controls.
- Modes
- First-party only.
- First-party
- Included. Crusible provisions the machine itself — that is what lets a shell outlive your laptop and your network.
- Connect instead
- Nothing to connect — Crusible provides this one.
- Who holds the record
- Crusible. There is no provider to hand it to.
- What it shows
- Shell output, terminal tabs, the selected machine and connection state.
- Controls
- Machine selection, terminal tabs, file uploads, diagnostics, Restart and Power off when available.
- Where this surface differs
- Access depends on the channel, its machine and the current session.
- What agents do here
- Agent engines can run in terminal sessions on the selected machine.
Terminal opens a shell on a machine associated with the channel. The machine runs commands; the browser displays the session. Closing the browser doesn’t send a command to stop those processes.
Machines, tabs and engines
The machine selector identifies the instance serving the terminal. Terminal tabs identify separate shells on that instance. Selecting a tab changes which shell receives input. An agent engine running in a shell can appear in the project’s Sessions list. The recognised engines are Claude, Codex and OpenCode. An engine name identifies the foreground program, rather than whether it’s taking a turn.
Header controls
The header contains connection and session state, shell information, file transfer, channel linking, diagnostics and available machine actions. Shell integration on means the shell supplies command information. Shell integration off means that information is unavailable; it doesn’t mean the machine has powered off.
Restart and Power off open confirmation dialogs. These actions affect the machine and can interrupt other work using it. A reconnect indication describes the connection, rather than promising that a command completed.
Files
Attach files opens a file picker. Dropping a file onto the terminal offers another upload path. The upload queue reports progress and failures. A successful transfer makes a file available on the machine; it doesn’t automatically send that file to the conversation. A watched terminal doesn’t accept uploads.
The terminal doesn’t expose a general download control, a port-forwarding panel, a browser-session manager or a secrets editor. File-transfer and preview actions elsewhere in the application have their own controls. Share a preview exposes a port in the Sandbox through a tunnel. Set a sandbox environment sets the environment variables and secrets a new shell starts with. Pasting credentials into a shell can expose them through saved commands or output.
Connection and access
The terminal reports connection failures and unavailable machines in the pane. A stopped machine and a lost connection require different responses. A machine shows “Lost the link” explains the connection checks. A machine idled out explains how to check the machine’s state.