CLI reference.

dove provision

dove provision <simple|full> [--bucket <name>] [--region <region>]
  [--profile <profile>] [--expire-days <days>]

• --region defaults to us-east-1.
• --expire-days defaults to 7 and controls S3 cleanup.
• Omit --profile to choose interactively.
• Provisioning always asks for confirmation.

dove share

dove share <file-or-directory> [--expires <duration>] [--encrypt]
  [--downloads <n>] [--pin [value]] [--from <name>] [--message <text>]

• --expires defaults to 3d. Accepted units are d, h, m, and s; values must be positive integers.
• Directories are zipped with the directory as the archive’s top-level folder. Symlinks are skipped.
• Full tier always encrypts. Its default download allowance is 100 when --downloads is omitted.
• --pin with no value generates a zero-padded six-digit PIN. A supplied PIN is used as given. The CLI does not currently validate it; use 4–6 numeric digits for compatibility with the browser page.
• --downloads only has an effect in full tier. The simple path currently ignores it rather than rejecting it. A value of zero creates a share with no usable download budget.
• --pin, --from, and --message are rejected outside full tier.
• Simple tier is capped at seven days. --encrypt creates encrypted bytes and a fragment key, but simple mode has no browser gate page.

dove request

dove request <description> [--from <name>] [--message <text>]
  [--pin [value]] [--expires <duration>] [--uploads <n>]

• File requests require a full-tier backend.
• --expires defaults to 3d; --uploads defaults to 1.
• --pin with no value generates a zero-padded six-digit PIN. A supplied PIN is currently used as given.
• The printed /r/<id>#fragment link contains the only copy of the fragment outside the requester’s local ledger. Treat it as a secret.
• The current browser flow accepts one file up to 512 MiB. --uploads is gate policy, not a multi-file inbox: the v1 request completes after one confirmed object.

dove requests

dove requests
dove requests get <id> [-o|--out <path>]

The list comes from ~/.config/dove/requests.json and refreshes each request’s live gate status. Statuses include waiting, received, failed, and unreachable. requests get downloads and decrypts a received request; waiting and failed requests do not fetch an object.

dove get

dove get <url-with-#fragment> [-o|--out <path>] [--pin <pin>]

No configured backend is required. The link identifies the host and carries the decryption secret. Full-mode metadata can provide the output filename; otherwise use --out or let dove derive a name from the URL.

Manage shares and backends

dove ls
dove revoke <id>
dove status
dove use <backend-name>

ls combines bucket keys with a local ledger. Full-tier object names are intentionally name-free; filenames appear only when the sending machine still has the matching local ledger record. revoke deletes the object early. use changes the active named backend in the registry.

Domain and gate controls

dove domain add <subdomain>
dove gate disable
dove gate enable
dove gate status

All four commands require a provisioned full-tier backend. Domain setup is interactive because it waits for you to add DNS records.

Interfaces that do not exist yet

The current CLI does not expose --json, stdin file uploads, batch shares, non-interactive provision confirmation, or a destroy command. Do not build automation that parses decorative progress output as a stable API. Use dove-core for typed results.