Skip to main content
tty7 speaks SSH itself, over russh. It never shells out to the ssh binary, and there is no compatibility mode that does. That is what makes the rest possible: credentials in the OS keychain, SFTP in a side panel, port forwards you can add mid-session, and authentication prompts drawn as sheets in the pane instead of a password echoing into your shell.
Connecting over SSH in tty7

Placeholder — screenshot: an SSH connection sheet asking for a key passphrase inside a pane

​
Four ways to connect

Open the palette (⌘ P) and type an address. IPv6 works with brackets.
Profiles live in Settings → SSH → Hosts. Start typing the name in the palette, or open the SSH: Manage Profiles… command.
Type an alias you already have and tty7 resolves it natively — common fields, best effort — then connects over russh. Settings → SSH → Import from ~/.ssh/config turns aliases into real profiles.
Match, canonicalize*, and GSSAPI directives are not supported, and there is no fallback to the system ssh when one appears.
The same connection can host whole workspaces on the far machine rather than a single shell. Remote workspaces →

​
Profiles

Settings → SSH → Hosts holds the full connection config. The basics: Defaults at the top of the list is inherited by every host, so a setting you want everywhere is set once. Passwords and key passphrases go in the OS keychain, never in config.json and never on disk in plain text. Forget Password in a profile’s menu removes the stored one. Deleting a profile drops its keychain credentials and forgets the remote workspace entries that connected through it — the confirmation counts them first. The sessions on the machine itself keep running; what happens to its entries →

​
Advanced

Behind Advanced on a profile, grouped: Everything blank means “the library default”, so you only fill in what you actually need to override.

​
Authentication prompts

Password, key passphrase, and 2FA prompts appear as sheets inside the pane, with a Remember (keychain) option where it makes sense.

​
Host keys

Host keys are verified against known_hosts by default. A first connection asks you to confirm the fingerprint; a changed key is a much louder prompt that makes you type yes to override, because that is what a changed key deserves. Settings → SSH → Security → Verify host keys turns verification off entirely. It is on for a reason. Also under Security: Warn before closing a live connection, off by default.

​
Reconnecting

⌘ ⇧ R — or SSH: Reconnect in the palette — restarts the session in the current pane. Useful after a laptop sleeps or a network changes.

​
What is not supported

  • No fallback to the system ssh binary
  • No Match or canonicalize* directives from ~/.ssh/config
  • No GSSAPI directives from ~/.ssh/config. Kerberos gssapi-with-mic itself is supported — pick GSSAPI in a profile’s Auth field — it is just not something the config-file resolution path reads