Termex -Help & FAQ

Add a server name, host, port, and username, then choose password, key, or automatic authentication. You can also add a jump host and any port forwards before the first connection.

Termex stops for host trust first. You must approve the server host key before the SSH session continues. If that key changes later, Termex warns and blocks the connection until you verify the new fingerprint.

Termex can import OpenSSH private keys and certificates. Some encrypted keys ask for a passphrase when you import them or when you first connect. Saved secrets stay in Keychain-backed storage.

Yes. Termex supports local, remote, and dynamic forwarding per server. If one forward fails, the app can show you which parts started and which parts did not.

When Keep one session alive is enabled, Termex creates or reuses one tmux session for that server so reconnects and relaunches can reattach instead of starting a new shell every time.

No. SFTP still works without shell integration. Shell integration only helps Termex detect the current remote folder automatically. If you use tmux, allow-passthrough must be enabled for those folder updates to survive tmux.

Termex follows the current remote folder reported by your shell. If that update has not arrived yet, it falls back to your SFTP home folder and tells you before upload starts.

You can upload local files and download remote files over SFTP during live SSH sessions. Existing files can be overwritten, renamed, or skipped. Termex does not currently provide a full folder-transfer workflow.

Server profiles, preferences, diagnostics, and known hosts stay local on your device. Passwords and private keys stay in Keychain-backed storage. Premium is managed through Apple, and the app includes purchase restore support.