Release notes · Sep 3, 2026

Termy 1.7.3: Local Terminal & SSH Workflow Update

Open a local terminal from anywhere, reuse your SSH agent, and connect through wildcard ProxyJump rules from your existing SSH config.

Current public builds require macOS 26 or later. See the latest release: 1.7.9.

Local Terminal

Command-T now works from Hosts. Open a new local terminal tab even when you are not already connected to a server.
Start Termy at a terminal prompt. A new Startup setting can open a local terminal automatically instead of restoring tabs or showing the Hosts list.
Local shells start in your home directory. Login shells now open in the macOS account home rather than the filesystem root or an app container.
Your SSH agent is available in local shells. Termy forwards a validated `SSH_AUTH_SOCK` or uses the 1Password SSH Agent when available.

Wildcard ProxyJump rules are applied automatically. Saved hosts now follow matching rules such as `Host *switch*.foo.com` with `ProxyJump proxy.foo.com`.
SSH Agent is available for saved hosts. Choose SSH Agent in the host editor to authenticate through `SSH_AUTH_SOCK` or 1Password without importing private keys into Termy.
Existing Termy routes remain authoritative. Explicitly configured ProxyJump chains continue to take priority over automatic SSH config matching.

Final-host authentication errors are reported correctly. If the jump host connects but the target rejects its password or key, Termy now identifies the target authentication failure instead of blaming the intermediate host.
Host-key diagnostics follow the failed hop. A successfully verified proxy host key is no longer mistaken for a host-key problem on the target.
Tunnel failures include actionable context. Connection logs now distinguish target negotiation failures from reachability and jump-host forwarding policy issues.
Recovery guidance keeps the configured route intact. Troubleshooting suggestions no longer recommend disabling ProxyJump or assume that saved Termy hosts exist in `~/.ssh/config`.