Vault operations
CLI 0.16.0 and Python 0.13.0 are published. These operations require the matching Vault backend. Check the Vault runtime memo for hosted availability; a local build or package release is not deployment evidence.
HOTP: take ownership explicitly
Import selected registrations as inactive by default. Stop other generators before explicitly activating DreamLake as the counter owner. For pass-otp, the stored counter is the last generated counter; activation normalizes it to the next unused value without writing back to pass. Initial activation supports SHA1 with at least a 128-bit seed; unsupported algorithms remain inactive.
Each new issuance needs a new private request-file path. After a timeout, process
restart, or uncertain response, reuse the same file, never a fresh one.
Its immutable account/origin/entry/revision/request metadata contains no seed,
code, counter or token. Both file and directory must support durable fsync on
POSIX; failures send no issuance request. Avoid shared or externally modified
request directories. Hardware/filesystems that ignore fsync cannot promise durability.
Receipts are encrypted and recoverable for 24 hours. This is a recovery deadline, not HOTP code expiry. Missing/expired receipts leave an ambiguous outcome; the original tuple cannot advance the counter again. Scoped retrieval keys cannot generate codes. General entry replacement cannot roll an HOTP counter back.
Entry expiry
vault add accepts an optional retrieval expiry. --expires-at takes an exact
UTC RFC3339 timestamp. Starting with CLI 0.95.0: --expires-in takes a
relative duration measured on the local clock at upload time and converts it to
the same UTC timestamp before the request is sent. Units are s, m, h, d
and w; whole numbers only, each unit at most once, for example 90d, 12h or
1w3d. --no-expiry explicitly clears an existing expiry. The three options
are mutually exclusive. Omitting all of them preserves the entry's current
expiry on replacement.
The stored timestamp is what the server returns in metadata; after the expiry, ordinary vault reads of the entry are refused until it is replaced. Match the vault expiry to the credential's own expiry so a stale copy never outlives the token it holds.
Metadata pages
Starting with CLI 0.43.1: when both stdin and stdout are terminals,
vault list opens a searchable, selectable metadata list. Use Up/Down to move,
Space to toggle entries, / to filter by name, Enter to return selected metadata,
and Escape or Ctrl-C to cancel. With no checkmarks, Enter selects the focused row.
Filtering preserves selections. No secret values are retrieved.
Pipes and redirected output retain JSON. --to-json explicitly requests JSON
even in a terminal. --tree remains the separate prefix-policy browser.
Default listings return all metadata by following 100-entry pages. Explicit pages
allow 1–200 entries and return nextCursor, or null at completion. Keep account,
prefix and retired filter unchanged. Traversal follows binary name order and is
not a snapshot: new earlier names require a fresh listing; deleted names can
vanish. No list operation reveals payloads. Legacy unpaged HTTP remains unbounded
until all consumers migrate.
Release a host reference
Use exact metadata from the saved binding. Unbinding works after host deletion, but preserve the binding receipt first. It does not revoke a remote key/password, delete an active secret, or bypass retired-entry retention.
Organization/team management preview (not released)
Discover scope IDs with dl vault scopes. Put --scope org:<id> or --scope team:<id> before supported entry or management commands. Personal remains the default; recovery keeps the original actor, scope and request ID, with no fallback on denial.
Use --destination-scope personal for an explicit personal destination. secret-copy --action status recovers committed identity; --action cancel permanently cancels a pending preview. Metadata never includes secret values. Preview expires after 24 hours, policy updates compare revision, and commits recheck source and destination authority. Export/policy requires org OWNER or direct-team MAINTAINER; ordinary entry CRUD remains member-based.
Copies retain the source and reseal a new destination entry. Source-retiring moves require a complete consumer inventory and remain rejected. Customer-KMS destinations need policy-aware reseal recovery and remain rejected. Shared OTP, KMS administration, keys, host/machine credentials and delivery are unsupported.
Shared-scope entry retirement (unreleased fix)
Use the immutable scope returned by vault scopes for every entry request.
The source correction allows the canonical vault delete entry operation in
org/team scopes; CLI 0.44.2 incorrectly rejects it before sending the request.
delete means retirement under the server's existing retention policy. There
is no vault retire command. Current membership is still checked by the server;
an organization owner does not bypass direct team membership.
Scoped entry list/show/get/add/delete/restore and write-status use the same
selected scope. Scope denial never retries against personal Vault. Shared OTP,
KMS/key administration, access keys, host bindings and remote delivery remain
unsupported. Do not remove those restrictions to support runtime consumers.
Use show for metadata; get explicitly retrieves secret values. An unavailable
capabilities endpoint does not imply that advanced operations are supported.