SSH connections

The SSH Connections tab lists saved hosts. Each connection has a set of fields including optional ones — grouping, jump host, start script and keep-alive.

Groups

Groups let you organize a fleet (e.g. Production, Staging, Customers). The edit form exposes a dropdown to pick an existing group or create a new one. Grouped connections also appear in the native menu bar (macOS) and as quick-access in the sidebar.

Jump hosts (ProxyJump)

When a target is only reachable through a bastion, mark the bastion with Jump host and point the target's Jump field at it. The chain can be as deep as you need — a jump can itself have its own jump.

Under the hood we use SSH direct-tcpip channels: a tunnel is opened through the bastion, then the real session runs through it. All inside the same process — no separate bastion session to manage.

From the CLI: dr-terminal connect prod1 -j bastion1,bastion2 (see Desktop CLI).

Start script

The Start script field carries a shell snippet sent automatically after successful login. Examples:

cd /srv/app && tail -F server.log

tmux attach -t main || tmux new -s main

The script is injected as regular input — the shell treats it exactly like keyboard typing. Afterwards the session stays interactive.

Keep-alive

If your server or firewall drops idle sessions, enable keep-alive. DR-Terminal then sends heartbeat packets at a chosen interval.

• Default — follow the global setting.
• On / Off — per-host override of the global default.
• Interval — 10–300 seconds, 30 by default.

Other fields

• Default SFTP directory — where SFTP opens after connecting.
• Save command history — remember commands for autocomplete.
• Show Enter key on toolbar — useful on mobile when you want a big Enter button.