Skip to content

v1.3.0-rc13

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Nov 17:22
Immutable release. Only release title and notes can be modified.

Release candidate for 1.3.0 - offered in the app on the release candidates update channel.

Shared catalogs: a connection tree your team shares from a self-hosted catalog server, kept in step on every machine, with each person's own credentials. Security fixes from an audit of the LLM (MCP) access, archive import and session sharing: each closes a way an untrusted input got more authority than the UI promised. Also: a VPN that needs a one-time code no longer asks for it again and again while you are away.

Shared catalogs

  • Attach a catalog (Settings -> Catalogs): sign in through your browser, or add it with a code from the catalog's web page (also in the Android app). Its folders, connections and port forwards appear under the catalog's root folder and follow it on every sync. The catalog server is a separate self-hosted service and not open source at this time; ssh-tool is the client.
  • Your own credentials stay yours: a credential from your vault and a network (VPN) profile are never sent. Colleagues set their own under My settings on a catalog folder or connection, like any other setting; without one the connection asks for the user name and password. Only a Bitwarden / Vaultwarden item or opkssh goes, as a slot each colleague with access gets by themselves, or binds once in a dialog on the first connect or from the connection's editor. Settings -> Catalogs lists the slots still to bind first and keeps the bound ones behind a filter.
  • My settings vs the catalog record: what you change on a catalog connection stays yours (port, username, notes, tags, icon) and can be reset. Writers edit the record itself for everyone, with a field-by-field view when someone saved first, and an offer to set a credential on the folder instead of each connection.
  • Publish a folder or a single connection into a catalog (right-click, or drag it onto a catalog folder): choose what to send (user names included), review every free-text value first, and keep your own vault credentials, VPN profiles and anything else local. A bastion outside the folder goes as a copy in it and one from a dynamic inventory as a bastion record made from its address (either can be left out), while you keep jumping through your own; uploaded icon images go to the catalog's image store.
  • Leave a catalog and keep its connections as a local folder, or copy part of it to your own connections. Records that left the catalog stay in your tree until you keep or delete them.
  • Catalog connections travel with profile sync and backups; an older app sharing your sync profile does not see them and leaves them alone.
  • Save as connection on a dynamic inventory host makes a fixed connection from what it resolves to now, and can point the jump hosts that use it at the new one.
  • Publish asks where when it does not know: the target starts at the one you used last on this machine, else at the top level (a new space) when you may create one, else empty until you choose. Before, it started at the first folder by name, which is some customer's folder.
  • Show only the catalog folders you work with: Settings -> Catalogs lists the catalog's folders with a tick for each one shown in your tree, and Hide in my tree on a catalog folder does the same from the tree. Hidden folders leave the tree, search and Quick Connect on all your machines and keep syncing; ticking them brings them back.
  • Match my connections (Settings -> Catalogs): if you had these hosts before the catalog, pair your own connections with the catalog's by host and port (the user name decides between several; you pick when that is not enough). Matching moves what was yours onto the catalog connection: credential (an unbound slot gets bound once for everyone using it), user, network, jump host, database and Kafka logins, settings the catalog leaves unset, notes and icon where it has none, saved passwords, favourites, forwards (one the catalog also has keeps your local port and bookmarks), workspaces, snippets and jump references. A value every connection of a catalog folder shares goes on the folder. Your copies are not deleted: they move to "Matched to " and keep working. The dialog groups the pairs by catalog folder with a tick per folder, and Undo last match puts it all back.
  • Publish preview lists each connection under its own folder: "What goes" showed the folders first and the connections after them, so with subfolders the connections looked as if they sat in the last folder listed.
  • "Slots to bind" counts only what is still missing: a slot every connection using it covers with your own value under My settings shows as "covered by My settings" and no longer keeps the catalog's warning chip up.
  • A catalog out of reach is a status bar issue, not a toast: when the catalog server cannot be reached (VPN down, working from home), the catalog shows under the issues badge for as long as it lasts and drops off with the next good sync; its connections keep working as last synced. A dead session still gets one toast, since it needs you to sign in.
  • A catalog can have its own icon: when the catalog server sets one (catalog protocol revision 5), it shows next to the catalog's name in Settings -> Catalogs and on its folder in the tree, already before you sign in. Without one nothing changes.
  • Move catalog records by dragging: a writer can drag a catalog folder or connection onto another folder of the same catalog, or a folder onto the catalog's top to make it a space. The move was there, but catalog rows could not be picked up.
  • The Delete key on a catalog record does what its menu does: "Delete for everyone" (with that confirmation) for a writer, the local delete for a record that left its catalog, and otherwise a note that it cannot be deleted. Before, it opened the plain delete prompt, which then failed.
  • Duplicate in the catalog: writers can duplicate a catalog connection in its folder with the same settings, slots and forwards, entering only the new name and address.
  • A catalog behind a VPN: a catalog can go through a network profile (Network, when you add it or under Edit). Sync now, sign-in, publish and your edits may bring the VPN up; the background sync only uses it when it is already up, and otherwise the catalog shows "waits for VPN" instead of a sync error.
  • Open in ssh-tool on the catalog's web page selects that connection, folder or slot in the app, syncing first when needed. A link never connects or runs anything; for a catalog this app is not attached to, it offers the catalog's connect page.
  • Shared bookmarks on catalog forwards (catalog servers from protocol revision 6): a catalog forward shows the bookmarks its record shares next to your own, and writers edit them under Catalog record. Your own bookmarks and their tree pins stay yours. Publishing sends a forward's bookmarks only when you tick Forward bookmarks (off by default), and lists their addresses in the free-text review. A bookmark with a {port} placeholder can be shared from revision 9.
  • Publishing keeps private Vaultwarden / Bitwarden items out on request: untick shared sources in "What to send", or a single credential in the review. If the folder changes after you reviewed it, the publish stops and shows the new review.
  • A catalog link (ssh-tool://) only fills in the enrollment form; nothing contacts the server it names until you click Check.
  • Catalog seats full: when every licensed seat of a catalog is taken, the app keeps you signed in and tries again on the next sync, showing the catalog's own message, instead of signing you out; adding a catalog with a code shows that message too instead of calling the code invalid.
  • Match my connections removes the local folders your copies leave empty (Remove folders left empty, on by default; Undo brings them back), so the old tree does not stay behind as empty folders.
  • No colour of your own on a catalog row: picking no colour under My settings on a catalog connection or folder now clears the catalog's colour for you; before, it fell back to the catalog's colour.
  • Slots for the whole catalog (catalog servers from protocol revision 12): an admin publishing several spaces that use the same opkssh or Bitwarden item gets one slot for all of them instead of one per space; the publish moves an existing slot of another space to the catalog level and reuses it, and new slots can be made catalog-wide. Colleagues bind it once.

Interface

  • Context menus no longer swallow the next click: a click outside an open menu (on a tab, the toolbar, the title bar) now does what it clicks. Before, it only closed the menu, and on the title-bar tabs on Windows it did not even do that.
  • Export dialog says what goes in: the options are now ticked for what the export includes (notes, tags, colour tags, icons, local shells, a connection's own credential link), instead of "Leave out of the export" boxes you ticked to remove something. The defaults are the same.
  • Drag a tab into a window that is already open: a tab dragged from the main window (or from one detached window to another) onto an open detached window now moves there. Before, it always opened a new window, so a tab could not be moved to the window on the other screen by dragging. Dropped anywhere else outside, it still opens a new window.
  • Pickers in dialogs show their whole list: the searchable picker (a Bitwarden, Vaultwarden or KeePass item when creating a credential, and the other searchable lists) was cut off at the edge of a dialog that scrolls, showing only "(inherit)". It now opens over the dialog, and upward when there is more room above.
  • Settings -> External secrets and Catalogs follow the theme: their buttons and fields had the browser's own look, which stood out in the light theme. The catalog's header in the connection pane no longer has its button sitting on the divider line.

LLM (MCP) access

  • Claude Desktop can run commands again: in its local agent mode Claude Desktop drops a tool argument named session_id, so run, read_terminal and the other session tools failed with "session_id missing". They now take session (the old name still works, Claude Code is unaffected).
  • A refused tool call says what arrived: when a tool's arguments do not fit (one MCP client was reported to lose them), the error and the app log name the argument keys and their types that came in, never their values, so the cause can be seen.
  • type_into_terminal never presses Enter: text with a newline or any other control character is now refused. Before, a carriage return in the text submitted the command at once, so the "review it and press Enter yourself" step could be skipped, and under read + run (YOLO) that also bypassed the prompt for dangerous commands.
  • ip read-only check is an allowlist: abbreviated write commands such as ip r d default or ip link c dev eth0 down were treated as read-only and ran without approval. Now ip runs without a prompt only with no command (the default listing) or with show, list, lst, get or help; everything else, abbreviated show included, asks first.

Import

  • Archive credential references no longer bind to your existing credentials by default: an archive could name the id of a credential already in your store and point a connection or a Proxmox dynamic folder it adds at it, sending that password or API token to a host of its choosing. Such references (login, jump host, TOTP, Kafka and database credentials) are now dropped, jump hops through one of your hosts are cleared, an archive folder matching one of yours that passes a credential down is imported as a new folder instead of merged, and Overwrite leaves alone every connection or folder that holds or passes down credentials (importing the archive's version as a new row), unless you tick the new Link to existing credentials option, meant for re-importing your own export. The dry run also warns when the Import into folder passes a credential down to the imported connections. With the option on, Apply needs a current dry run. The dry run lists which credentials would be linked or were left out.
  • The dry run now lists every connection an Overwrite import points at a different host or port, since such a row keeps its saved password unless the archive restores one; warnings are shown in the preview, not only after applying.
  • Argon2 parameters read from an archive or a vault file are range-checked before deriving a key. Zero values used to fail the import and a huge memory value could crash the app.

opkssh

  • opkssh 0.20.0 (OpenPubkey 0.30.1): upstream security fixes, among them a refreshed ID token whose signature was not checked under the OIDC_REFRESHED policy and a group policy parsing edge case.

VPN

  • No more login prompts every two minutes while you are away: when a VPN session that needs a typed one-time code (or a push) expired with a Kafka or Database tab open through it, the tab kept reconnecting in the background and every try started a new VPN login with a new prompt, all night long. A tunnel's own reconnects did the same. Now a login started in the background that does not finish puts the profile on hold, as the app proxy already did: background connections through it fail at once, you get one notice, and everything resumes when you connect the profile or open a connection through it.

Plugins

  • The plugin update toast opens cards with the Update button: with Settings already open on Network profiles, clicking the toast showed the cards read before the update came out, without the button, until you left the section and came back. The cards are now read again when the toast opens them and whenever the background check finds a new plugin release.

Session sharing

  • Join code per connection: the guest page shows a fresh code for each connection, and the approval prompt shows the code of that request, so you allow only the request your guest reads to you. The four words compared before were the certificate fingerprint, the same for everyone holding the link, so they could not tell your guest apart from someone else. The share dialog now gives the certificate SHA-256 to send your guest, who checks it in the browser's certificate details; the words on the guest page cannot detect an intercepted connection by themselves, and the user guide no longer says they do.