Take Command can open a tab window with an SSH connection. SSH connections use the Take Command scrollback buffer and support search, recording, annotations, terminal triggers, and accessibility features. They do not run a shell, so shell-integration prompt marks and command folding are unavailable.
OpenSSH prompts appear in the SSH terminal tab. Verify a host-key fingerprint before accepting an unfamiliar key. Use the strict host-key policy for managed or sensitive hosts whenever possible.
Enable Use jump host in an SSH profile and specify its host, port, and user. Take Command creates a validated single-hop ssh -J connection. The jump host is part of the connection profile; Quick Connect does not save it.
Set Server alive interval and Server alive count max when an SSH server or network device drops idle sessions. These become OpenSSH keepalive options. Use conservative values appropriate for the remote environment; an excessively short interval can create unnecessary traffic.
SSH profiles can run ordered, session-scoped expect/send login-script steps after connecting. Use these only for predictable banners or prompts that cannot be handled by normal OpenSSH authentication.
•Each step is a regular-expression expectation followed by text to send.
•Each step has a timeout from 100 ms through 60 seconds.
•At most 16 steps and 8 KiB of total script data are accepted.
•The script belongs only to that SSH session and is discarded with the tab.
Do not put a password, passphrase, or other durable secret in a login script. Use the vault and standard OpenSSH authentication instead.
Open an SSH profile and select Port Forwarding... to define forwards. Forward definitions are typed profile values, not arbitrary OpenSSH command-line text. Changes take effect the next time the session connects or reconnects.
Type |
OpenSSH option |
Purpose |
|---|---|---|
Local |
-L |
Makes a local listening port reach a remote destination. |
Remote |
-R |
Makes a remote listening port reach a destination from the remote side. |
Dynamic |
-D |
Starts a SOCKS proxy listener. |
For each rule, enter a bind address, listen port, destination host/port when required, and enabled state. Ports must be in the range 1 through 65535.
An empty bind address is loopback-only by default. A non-loopback bind requires acknowledgement because it exposes the listener to other systems. Do not expose a forward to an untrusted network unless that is intentional and protected separately.
Use the active-session SSH Forwarding Status dialog to view the immutable rules configured for the current connection and any redacted OpenSSH forwarding diagnostics. It does not modify a running session.
X11 forwarding is off by default.
•Enable standard X11 forwarding to use OpenSSH -X.
•Enable trusted X11 only when required; it uses -Y and gives the remote application broad access to the local X server.
•Take Command checks that DISPLAY is available before launching. It does not install, start, or configure an X server.
Agent selection controls local authentication; agent forwarding is a separate opt-in that lets the remote host request signatures from the selected agent.
•Default uses normal Windows OpenSSH agent discovery.
•Windows OpenSSH Agent requires the Windows ssh-agent service to be available.
•Disabled prevents agent discovery.
•Pageant is deliberately unavailable until a compatible OpenSSH-agent transport is verified.
Enable agent forwarding only for hosts you trust. A forwarded agent may be used by remote processes to request signatures while the SSH connection is active.
The following related capabilities are planned or intentionally not available yet:
•An integrated SFTP browser panel.
•ZMODEM send/receive support.
•More than one SSH jump-host hop.
•Changing SSH forwards while a session is running; edit the profile and reconnect instead.
•Pageant agent transport.