Skip to main content
abadge export walks the active profile’s server-managed items and prints them as either an .env file or JSON. Zero-knowledge items are skipped — they require local decryption through the daemon and are not exportable through this command.

​
Usage

​
Flags

Export always uses the active organization’s server-managed items. To target a different scope, switch orgs with abadge org use.

​
env format

One line per item: the label is normalized to a POSIX env-var name (openai-api-key → OPENAI_API_KEY) and the value is taken from the item’s fields.value. Values containing newlines or quotes are double-quoted and escaped. Items whose payload has no value field fall back to a JSON-serialized value.

​
json format

A flat object mapping each item’s label to its value:

​
Audit

  • item.export — emitted once per export run with the item count in meta.

​
Constraints

  • Server-managed items only.
  • Permissions are not enforced at the API level for owner reveal (the operator owns all items in their orgs), but the audit trail records each read.
  • Export does not include encryption material, IVs, or other internals.

​
Why no ZK export

Exporting zero-knowledge items would require decrypting them through the daemon, then re-emitting them as cleartext. That’s a one-line for loop with abadge item get --reveal if you really need it, but the explicit gap is intentional — export is for moving server-managed items between deployments or backing up a profile.