A full SSH client, in the window with your agents.

The terminal you expected

Interactive terminal sessions on any host you’ve added, with the same rendering and scrollback as the rest of the app. A session is a pane like any other — split it next to the agent that’s deploying to the same box.

Per-host command snippets save the incantations you always retype — name plus command, persisted per host — and a `tail -f` log viewer watches a file on the server without a second session.

Files, both directions

The dual-pane file manager drags and drops between local and remote over SFTP or rsync. Resume picks up an interrupted transfer where it stopped (needs rsync 3.1+ on both ends; otherwise it falls back to SFTP without resume). Conflicts get a four-way choice instead of a silent overwrite, and uploads stage to a temp path then swap atomically — a killed transfer never leaves a half-written file on the server.

Tunnels that know when they’re dead

Local, remote and dynamic port forwards with live state. Dead-session detection means a wedged tunnel flips to reconnecting instead of sitting “live” forever on a dead socket.

See the host without leaving

The host monitor shows the top-20 CPU processes and disk usage, live, in the same window. Enough to answer “why is the build slow” without opening another tool.

Strict about who you’re talking to

Anything non-interactive — transfers, tunnels, scripted commands — refuses a host key it has never verified. The interactive terminal is the one place a key can be adopted: on a key-auth host you see the fingerprint first and accept; on a password-auth host the first connect adopts it, on macOS and Linux. A key that has changed is refused everywhere.

Key authentication works on macOS, Linux and Windows. Password authentication is macOS and Linux only — refused on Windows up front, rather than failing mid-connect.