Changelog
User-visible changes only. Internal refactors and test work don’t appear here.
Because there are no public builds yet, this starts as a record of what exists rather than a list of releases. It becomes a normal changelog with the first early-access build.
0.1.0 — unreleased
Section titled “0.1.0 — unreleased”The first complete version: desktop app, CLI, and the zero-knowledge server.
Vault
- Projects and environments, with drag-to-reorder tabs shared across the team
- Three entry types —
secret,url,env— withenvrendering unmasked - Masked-by-default values, per-row reveal, notes treated as secret material
- Copy to clipboard with a ~20-second auto-clear, surfaced in the toast
- Multi-line and file values; paste a whole
.envinto the add drawer - Payload version history
Locking
- Lock on 15 minutes idle, on every platform
- Lock on sleep, display sleep, and screen lock — macOS only for now
- Key material zeroized on lock; revealed values collapse
Teams
- Invite by email with a single-use token, 7-day expiry, revocable
- Two-step handshake: accept and publish a key, then admin confirmation
- Mandatory out-of-band fingerprint ceremony before any key is wrapped
- Per-environment grants: no access, read, or write. New members default to no access
- Atomic revoke-and-rotate with key epochs
- Roster, role changes, and member removal
Sync
- Optimistic concurrency with a client-side 3-way merge
- Per-key conflict prompts; never a silent last-writer-wins
- Durable version high-water mark, so a replayed older payload is refused
Recovery
- Personal recovery with the Recovery Key — key pair unchanged, grants intact
- Admin-assisted recovery with a new key pair, for shared environments
Audit
- 33 recorded action types, including every read of an environment’s payload
- Admin- and owner-gated, per project
CLI
cendarum run— inject an environment into a child process; nothing written to diskcendarum import—.envto encrypted payload, with duplicate keys refusedcendarum export— the friction’d escape hatch, with a git-working-tree guard- Exit-code passthrough and signal forwarding
Known gaps in this version
- No signed or notarised installers
- Sleep and screen-lock auto-locking on Windows and Linux
- No offline reading of secrets
- No CI or headless support
- The per-framework compatibility matrix has not been run end to end
- Link sharing is specified but not implemented
See the roadmap for what happens to these.