v0.1.16

Things that were quietly wrong. No new features — four fixes, all of the same kind.

Fixed

Deleting a server asks first, and says what goes with it. It used to be one tap on a menu, with no confirmation, taking the saved password or key selection with it. The question now names what is attached to that server: how many sessions will close, how many saved tunnels go too, how many other servers connect through it.

Deleting a server no longer leaves its session running. The tab stayed in the terminal, the notification stayed up, and its forwards kept going — all pointing at a server that was no longer in the list. Its saved tunnels also stayed in the vault forever, unstartable, because their server was gone.

Deleting a private key asks first. This was one tap with no confirmation at all — less friction than removing a Docker container, for the one thing in the app that genuinely cannot be recovered. It now also says how many servers authenticate with that key and will stop connecting.

Tunnels stop when the session carrying them ends. A tunnel travels through one SSH session; when that session closed, the forward was dead but stayed listed as running — and its local port stayed bound, which is why starting a replacement on the same port failed with "address already in use". Closing a session, or giving up on reconnecting, now stops what it carried and says so in the timeline.

The dashboard's tunnel counter was the literal string "0". It had said zero with tunnels running since the first release. All three counters now go to the screen they are counting, too.

What deleting a server deliberately leaves alone

• The timeline. The history of a server you deleted is still history.
• The known host key. It is the same machine tomorrow, with the same key.
• The jump-host setting of servers that route through it. Clearing it would quietly turn a routed connection into a direct one. Those connections fail loudly instead — which is the entire point of having set a jump host — and the delete dialog warns you before it happens.

Upgrading

Installs straight over v0.1.15. Same signing key, so your servers, keys and timeline are untouched.

Checksums

b6dbe26ac8a1d1ad5d2ecfa91ed330670be45a7d10c5613bc3f98e8cf5c087ea  CubePilot-v0.1.16-android.apk
1a1d16fbfcc19d71364ee07d717d981dddc749cc2501f0129d4c934388ee4125  CubePilot-v0.1.16-windows-x64.zip