> ## Documentation Index
> Fetch the complete documentation index at: https://doc.trycapsule.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Changelog
> Release history for the Capsule CLI agent. Alpha releases are included.
## v0.1.3-alpha.7
**July 1, 2026** · Alpha
### Added
* **Daemon auto-update** — when a new CLI release is published, every connected daemon receives a signal over its existing SSE connection and updates itself automatically. The daemon downloads the new binary, verifies the SHA-256 checksum, replaces itself in place, and exits — systemd restarts it with the new version. No manual `capsule update` or service restart needed.
* **Instant plan sync** — plan changes made from the HQ admin panel or triggered by Stripe (upgrades, downgrades, cancellations) now propagate to the CLI immediately over SSE. The plan cache is cleared on the daemon side as soon as the change lands, so the next TUI open reflects the correct plan without any manual refresh.
* **`CTRL+R` plan refresh in TUI** — manually re-fetch your current plan from any TUI screen. Useful immediately after upgrading your plan if you want to unlock features without restarting the daemon.
### Changed
* **Schedule option hidden for Hobbyist users** — the Schedule entry no longer appears in the database menu for accounts on the Hobbyist plan. Previously the option was visible but produced no response when selected.
***
## v0.1.3-alpha.6
**June 22, 2026** · Alpha
### Added
* **Disaster restoration** — you can now restore a backup to a completely different server or database instance, not just the original source. Useful for migrating data or recovering into a clean environment after an incident.
***
## v0.1.3-alpha.5
**June 20, 2026** · Alpha
### Added
* **Pre-deploy backup trigger** — the daemon now listens for a pre-deploy signal from the dashboard. When you kick off a deployment, Capsule automatically takes a backup before your code runs so you always have a restore point tied to that exact state.
* **Real-time backup status** — backup progress and completion are now reported back to the dashboard over SSE as they happen. You no longer need to refresh to see whether a backup triggered from the dashboard succeeded.
***
## v0.1.3-alpha.4
**June 19, 2026** · Alpha
### Added
* **`capsule doctor`** — new diagnostic command that checks whether all required tools (`pg_dump`, `mysqldump`, `mongodump`, Docker, etc.) are installed and reachable. Run it after installation to confirm your environment is ready, or when a backup fails and you want to rule out missing dependencies.
* **End-to-end tests** — automated coverage for backup, restore, and schedule flows across PostgreSQL, MySQL, and MongoDB on both Docker and native connections.
### Fixed
* Credentials are now injected via environment variables when running backups inside Docker containers, instead of being passed on the command line. This prevents credentials from appearing in process lists.
***
## v0.1.3-alpha.3
**June 19, 2026** · Alpha
### Added
* **MongoDB restore** — you can now restore MongoDB backups from the CLI, not just create them.
* **Pre-restore snapshots** — before a MySQL or MongoDB restore begins, Capsule takes an automatic snapshot of the current state. If the restore fails or you change your mind, you have a rollback point.
### Fixed
* PostgreSQL restores are now atomic. If any step fails, the operation rolls back cleanly instead of leaving the database in a partial state.
* Error messages from failed restores now surface correctly rather than being silently swallowed.
### Security
* Credential files are overwritten with random bytes before deletion, preventing recovery from disk.
* API responses are validated to prevent tampered data from being written to disk.
* Several additional hardening measures to reduce the risk of credential leakage during backup and restore operations.
***
## v0.1.3-alpha.2
**June 18, 2026** · Alpha
### Changed
* **Redesigned keyboard hints** in the TUI — navigation keys are now displayed in a clearer key → action format, making it easier to discover what you can do from each screen without reading the docs.
***
## v0.1.3-alpha.1
**June 18, 2026** · Alpha
### Fixed
* Backups no longer fail with a 400 error when a connection has no label set. Capsule now catches this before making the API call and shows a clear message instead.
***
## v0.1.3
**June 18, 2026** · Stable
### Fixed
* Connection labels were displaying incorrectly in certain list views. Labels now render as expected.
***
## v0.1.2
**June 18, 2026** · Stable
### Fixed
* Corrected the source URL used to download CLI updates via `capsule update`. Self-update now pulls the correct binary for your platform.
***
## v0.1.1
**June 18, 2026** · Stable
### Added
* **Dashboard-triggered backups and restores** — the CLI daemon now listens for on-demand backup and restore requests sent from the web dashboard over SSE. You can trigger a backup from the dashboard without logging into your server.
### Changed
* Updated README with installation instructions and usage examples.
***
## v0.1.0
**June 17, 2026** · Stable
The first tagged release of the Capsule CLI.
### Added
* **`capsule schedule`** subcommands — create, list, pause, resume, and delete backup schedules from the command line without opening the dashboard.
* **Scheduled backups** — the daemon runs `pg_dump` / `mysqldump` / `mongodump` on your configured schedule, encrypts the output locally, and uploads it to cloud storage.
* **`capsule update`** — self-update command that downloads the latest binary for your platform, verifies the SHA-256 checksum, and replaces the running binary in place.
* **Version enforcement** — the CLI checks the minimum required version on startup and blocks commands if the installed version is too old, prompting you to run `capsule update`.
* **Plan enforcement** — CLI commands respect your account plan. Features unavailable on your current plan show a clear upgrade prompt.
* **Disk-cached version checks** — the version check result is cached to disk for 30 minutes, so every command doesn't make a network round-trip.
* **HMAC-signed local caches** — plan and version caches are signed to detect tampering. The CLI will reject and re-fetch any cache file whose signature doesn't match.
* **OS keyring integration** — your license key is stored in the system keyring (macOS Keychain, Linux Secret Service / `pass`), not in a plaintext config file.
* **Splash screen** — a branded ASCII splash screen on first launch that auto-dismisses after 2 seconds or on any keypress.
* **CI workflow** — GitHub Actions workflow for building and publishing release binaries.