What's new
What changed in each RescueShell release, newest first.
0.2.4 · 18 November 2026
- New: Your first device is free to try, with no card. The 30-day trial starts when that device first connects, not when you sign up.
- Until you add a card, shell traffic is capped at 50 MB in total, and a second device needs a card. With no card, use ends 30 days after the first device connects, or when the 50 MB is used, whichever comes first. Free first devices are limited per network. A card added during the trial does not restart or shorten it.
- New: If a shell ends because the 50 MB is used, the command-line client now says so and points you to the Billing page.
- Agent: 0.2.3 (unchanged)
0.2.3 · 18 November 2026
- New: The agent can update itself to the newest signed release. It checks the signature and the file hash before swapping, keeps the previous binary, and rolls back if the new one never holds a connection. It updates about once a day, and only when no shell is open.
-
New: A team can turn automatic updates off. A device can also be locked off
on its own with
install.sh --no-auto-update. - Agent: 0.2.3. Devices still on an older agent need one manual install of 0.2.3 before they can update themselves.
0.2.2 · 18 November 2026
-
Fixed: Re-running the installer with
--reregisteron the same host reuses the existing device row instead of creating a duplicate. - Fixed: If the passkey for a saved key is not on this device, the message now says so and points to "Use a different key" and "Lost your passkey", instead of only saying the prompt was cancelled.
- Agent: 0.2.2
0.2.1 · 16 November 2026
-
Fixed: The first connection accepts the full output of
rescueshell-agent --statusand matches the host key the agent announces. - Fixed: "Remember this key" no longer creates a new passkey every time. Opening a shell asks for one passkey confirmation.
- Agent: 0.2.1
0.2.0 · 16 November 2026
- New: A multi-use enrolment pass so you can install many devices with one command. Attested devices can be pinned automatically, without pasting a host key on each one. Longer or never-expiring passes can require approval before a device is accepted.
- New: Device groups, group keys, and signed trust changes for a group from the browser or the CLI. Our servers store and relay a change; they never sign it.
- Agent: 0.2.0