A jump host can now be any saved connection or inventory host, defined
once. Plus clearer tunnel port conflicts and more connection settings.
Jump hosts
- A jump hop can now be a saved connection or a host from any inventory
folder (Proxmox, Hetzner, DigitalOcean, Linode, Vultr, Scaleway, AWS
EC2, Ansible) instead of a typed-in host. Pick "Saved connection" on the
hop: the bastion's address, user, credential and its own jump chain are
read from it at connect, so changing the bastion once changes every chain
through it. An inventory host follows its address from the last refresh. - A bastion inside the folder it is the jump host for connects directly,
and its neighbours go through it. - Connect errors name the bastion by its connection name.
- Deleting a connection that other chains jump through warns first.
- Bastions are marked in the tree with how many use them, a folder that
sets a jump chain carries a route mark, and the connection detail lists
who jumps through it, each entry one click from the tree. Settings ->
Connection tree chooses Off, Bastions only (default) or Bastions and
routed connections. - The tag filter gets a Role group: role:bastion (inventory hosts
included) and role:behind-bastion. The Via filter names a saved-
connection bastion. - The connect order shown in the editor tooltip and the "inherited" hint
was reversed for chains of two or more hops. - A host that does not answer behind a bastion, or accepts the connection
but never completes the SSH handshake, now fails after the connect
timeout instead of staying on "connecting".
Tunnels
- A local port that is taken says who holds it: another tunnel (by name
and connection), another program, or a Windows reserved port range.
"Start on a free port" runs the tunnel once on a free port, keeping the
saved one. - The tunnel editor warns while you type a port that is in use or set on
another saved tunnel. - Tunnels that start on their own (auto-start, after a reconnect) report a
failed start, and an auto-port tunnel says when it could not get its
previous port back. - The tunnel popover and the quick palette showed some errors as raw JSON.
MCP
- The provisioning tools take jump_connection: a saved connection, an
inventory host or one created earlier in the same plan as the bastion,
on create_connection, set_folder_settings and now edit_connection too.
An inline jump host that matches a saved connection gets a hint to
reference it instead.
Settings
- Settings -> Connection adds auto-reconnect attempts and the longest wait
between them, Connect all parallelism, pause and confirm threshold, and
how long a shared bastion connection stays open after its last session. - Tree-row options (colour tag as background, active row emphasis) moved
from Appearance to the new Connection tree section. - Resolved & inherited sits at the bottom of the connection detail and
starts collapsed.
Under the hood
- Wails v3.0.0-beta.28 (from beta.18): among others, the window recovers
when the WebView2 process fails instead of staying blank, and a right
click on the Linux tray icon no longer also runs the click action. - opkssh 0.16 / openpubkey 0.25. opkssh 0.16 changes how GQ signatures
are verified: with GitHub as the provider and GQ signing, a client and
a server on different sides of 0.16 do not accept each other's
signatures. Other providers are not affected. - The opkssh login opens the browser through the same launcher as every
other link, with no console window. - Go 1.26, newer x/crypto, x/net, SQLite driver, SFTP and MCP SDK.
Fleet tools
- Running a fleet tool on a folder includes hosts of inventory subfolders
that were never expanded. - Saved connections and inventory hosts selected together (Ctrl+click) can
go into Compare file and the other fleet tools as one set. - The TLS certificate check reaches a host the way a connect does: through
its jump chain or network profile, so bastion-only hosts no longer fail.