SSH connections

Scope and prerequisites

Use a build containing SSH support, an authorized host and a reachable SSH service. Know the username and whether password, a saved credential or a registered private key is required. A proxy test does not prove the final host is reachable.

Create a connection

1. Open File → New SSH Connection. Give the session a recognizable name and choose a local folder if needed.
2. Enter the administrator-provided host, without an ssh:// prefix, and its SSH port (normally 22). server.example.invalid is a documentation example, not a working target.
3. Choose authentication. For a key, reference a registered local key and the correct remote username; for saved credentials, select the intended record.
4. Select a configured SSH proxy only when needed. A local session folder does not change the remote working directory.
5. Connect. Verify both jump-host and destination fingerprints independently where applicable. Stop if a fingerprint unexpectedly changes.

Check the connection

A connecting screen means the attempt is in progress. A failed screen needs the reported error addressed. An interactive shell plus a permitted read-only command such as pwd or hostname helps confirm the actual target. Do not put secrets into session names or screenshots.

Disconnect and reconnect

Use the reconnect control offered by the disconnected tab. Reconnection starts a new shell: it does not guarantee that the previous foreground process survived. Check each split separately and confirm the target before typing. Initial connection retries are separate from recovery after an established connection is lost.

Common problems

For a timeout, check host and port, VPN, routing, network egress and proxy configuration. For authentication failure, check the username and selected password/key material; repeated retries may lock an account. For changed host keys, stop and ask the administrator. See Troubleshooting.

Command suggestions and host policies in v3.2.19

Supported Zsh, Bash and PowerShell environments provide command, path and argument candidates with keyboard selection and pagination. Dynamic options and subcommands are discovered from available command help, including remote Bash over SSH from Windows. Availability depends on shell support and remote help content. Host command rules can be managed independently and explicitly copied with conflict detection. Check the target host and scope before saving; suggestions do not bypass command policy or approval.