Use your SSH config as the source for a Termy connection.

Define a host and its jump route

This illustrative OpenSSH configuration defines a bastion and an application host. Replace the example names, addresses and users with values you are authorized to use. The second destination is resolved from the jump host’s network.

The example deliberately omits key paths. Authentication remains a separate choice: use your saved Termy credentials or the configured SSH agent.

Host bastion-example
  HostName bastion.example.com
  User operator
  Port 22

Host app-example
  HostName 10.0.0.12
  User deploy
  ProxyJump bastion-example

Link the alias in Termy

In the host settings, choose SSH Config as the route and enter app-example. Preview the resolved destination and jump route before saving. Review the final user, port and host, rather than relying only on the friendly alias.

The SSH config importer can also keep imported hosts linked to the default config. A manually configured host remains independent unless you explicitly choose the linked route.

Understand when changes take effect

Termy re-reads linked connection settings before every new connection and reconnect. Editing the config updates the next resolution; it should not be treated as changing the network route of an already established shell.

The default config belongs to the Mac making the connection. When using another Mac, make sure its aliases and Include files exist and resolve to the intended destination.

Keep routing and authentication separate

For matching jump hosts, Termy can reuse saved credentials. Other hops can use the target host’s configured authentication. Multi-hop and nested ProxyJump chains are supported, but every hop still needs a valid route and authorization.

Termy does not open private keys simply because an IdentityFile appears in the config. It uses saved authentication or your SSH agent. That distinction is especially useful when keys are managed by an external agent such as 1Password.

Resolve unsupported or unsafe routes explicitly

Invalid ports, malformed or cyclic jump chains and ProxyCommand routes fail with an error rather than being bypassed. Match and ProxyCommand commands are never executed.

If a route is rejected, inspect the resolved alias and included configuration. Replace an unsupported route only when you understand the equivalent supported network path; do not assume Termy implements every OpenSSH configuration directive.

• Check that the alias exists on the current Mac.
• Inspect Include files and each ProxyJump hop.
• Validate hostnames and port numbers.
• Check authentication separately for the target and jumps.
• Use the compatibility documentation for supported behavior.

Common questions

Keep exploring

• Native SSH Client for macOS
• Termy 1.7.9 release notes
• Platform and integration compatibility