Connect with Quick Connect#
Type a user@host:port destination and open an SSH session without saving anything.
Quick Connect is for hosts you do not want to save. You type a destination, give a password if the host needs one, and you are in. Remote Terminal writes nothing to your profile library. Use Quick Connect for a machine you visit once, and a saved profile for one you come back to.
Connect from the toolbar#
The Quick Connect field takes a destination in the form user@host:port.
Both the user and the port are optional. Leave the user off and Remote Terminal connects as root. Leave the port off and it uses 22. So example.com and root@example.com:22 do the same thing.
Press Enter or select Connect. A password field appears beneath the destination you typed. Type the password and select Go. To authenticate with a key instead, leave the field empty and press Enter. Press Escape to cancel.
As you type, the field suggests matching saved profiles, up to five at a time, matched on profile name, host, or username. When you select a suggestion, Remote Terminal connects through that profile with its stored credentials, and does not treat what you typed as a new destination.
If the text does not parse as a destination, nothing happens when you press Enter. There is no error message, so check the format if a connection does not start.
Connect from the New Session panel#
SSH Quick Connect in the New Session panel does the same job with separate fields rather than one string. Host and Username are required, and Connect stays disabled until both have a value. Port defaults to 22.
Fill in Password to authenticate with a password. To use a key instead, leave Password empty and give a Key Path such as ~/.ssh/id_rsa. Enter connects from any field.
Note Quick Connect has no jump host and no on-connect command. If you need to reach a host through a bastion, or run a command automatically on login, save a profile instead. Both fields are described in authentication and profile fields.
What Quick Connect does not remember#
Remote Terminal uses a Quick Connect password for that connection and then discards it. The host, port, username, and any key path go to Recent so you can reconnect, but the password is not stored anywhere.
This is why a reconnect to a password host from Recent asks you for the password again, and a reconnect to a saved profile does not. See recent connections.