Use the web terminal

The web terminal gives you a live shell to any connected server right in your browser — no SSH client, no keys to manage. This page covers opening it, copy and paste, keyboard shortcuts, and reconnecting after a drop.

Open the terminal

Copy and paste

The terminal supports copy and paste so you can move commands and output around freely:

• Copy — select text in the terminal; use your usual copy shortcut (Ctrl/Cmd + C). Because Ctrl + C also sends an interrupt to the running program, copy works on the current text selection — if nothing is selected, Ctrl + C interrupts instead.
• Paste — Ctrl/Cmd + V pastes clipboard contents at the prompt. You can paste multi-line commands.

Terminal toolbar

The terminal header carries a few conveniences, none of which touch the running shell:

• Search (Ctrl/Cmd + Shift + F) — a search bar over the scrollback with next/previous and match highlighting. Enter = next, Shift + Enter = previous, Esc closes it. Plain Ctrl + F still goes to the shell.
• Copy scrollback — copies the whole buffer to your clipboard (ANSI codes stripped).
• Clear — clears the screen (like Ctrl + L).
• Preferences — font size and scrollback length, remembered in this browser.
• Fullscreen — expand the terminal to fill the window.

You can also re-run any past command: on a row in the command history, the re-run button pre-fills the background-command runner with that command (it still runs signed, after your review — nothing executes on its own).

Keyboard shortcuts

The terminal behaves like a standard shell. The essentials:

Shortcut	What it does
Ctrl + C	Interrupt the running command (or copy the selection)
Ctrl + D	Send end-of-file / exit the shell
Ctrl + L	Clear the screen
Ctrl/Cmd + V	Paste at the prompt
Ctrl/Cmd + Shift + F	Search the scrollback
↑ / ↓	Scroll through your shell command history
Tab	Autocomplete paths and commands

Standard shell editing shortcuts (Ctrl + A, Ctrl + E, Ctrl + U, Ctrl + R reverse-search, and so on) also work, since you're talking to the real shell on the server.

Reconnecting

If your connection drops — you close your laptop, switch networks, or the browser tab sleeps — the terminal session ends. To get back in:

Pinning a terminal

A terminal normally lives on its server's page: leaving the page closes the view. The pin button, top-right of the terminal, moves it into a panel docked to the bottom-right of the screen — and that panel survives navigation. You can watch a build finish while reading the monitoring tab, or while working on another server.

Up to five servers can be pinned at once, each with its own tab. The panel folds away with the chevron without closing any session.

A pinned terminal leaves the server page, which then shows a short card with two buttons: show the panel, or detach to get the terminal back in place. This is not an arbitrary restriction — a shell session is identified per server, and two terminals open on the same host would attach to the same process, each resizing the other's window and splitting the keystrokes between them.

For the same reason, opening a pinned server's file explorer detaches it automatically: the explorer already carries a terminal of its own.

Recording and replaying sessions

For audit or training, a team can have its terminal sessions recorded. An admin turns it on in Settings › Team › Team security; it is off by default, because recording what operators see is something a team decides, not something that happens to them.

Sessions then appear in the Terminal sessions panel on the server's page: who connected, when, from which address, and for how long. A recording replays in a real terminal — colours, cursor moves, a top redrawing itself — so what you watch is what the operator had in front of them, not an approximate transcript.

Two things worth knowing: a very noisy session (a tail -f left running) is truncated past a certain size and the replay says so; and even with recording off, the session list keeps filling up — knowing who opened a terminal and when is already an audit answer.

A session appears as soon as the first key is pressed, marked live for as long as the shell is alive. That is deliberate: closing the tab does not kill the shell, it detaches and keeps running — so the list also says who is on the machine right now.

Opening a terminal and closing it again without typing anything leaves no trace: there is no session to audit where nobody did anything, and a list full of empty openings is a list people stop reading.

When a session has nothing to replay, the list gives the reason rather than a flat "not recorded": Recording off (the team setting was off when the shell opened — turning it on does not retroactively capture a session already running), Recording (the shell is still alive), No output (nothing was ever printed), or Recording failed, which flags a genuine storage incident and shows the detail on hover.

See also