SEAL CLI

Encrypt locally, upload ciphertext, get a share link, from any terminal, headless server or CI job.

Install

curl -fsSL https://seal.net/install.sh | sh

Auto-detects OS / arch • verifies sha256

The installer detects your OS and architecture, downloads the matching binary and verifies its SHA-256 checksum before placing it on your PATH. macOS and Linux, including headless environments.

First seal

seal keygen                 # one-time: create your local identity
# in CI: export SEAL_SEED=... (from seal keygen --export --force)
seal send contract.pdf --ttl 1d

# → share link  https://seal.net/s/<id>/<code>#<key>   (give this away)
# → manage link https://seal.net/s/<id>#<key>          (keep this)

The encryption key rides in the URL fragment (#…). Browsers never send fragments over the network, so the SEAL backend cannot read it even if it wanted to.

Commands

seal send <files…> [--message <text>]Encrypt and upload; prints share + manage links and a QR.
seal receive <url>Download and decrypt a seal into the current directory.
seal request --what <text>Ask a person for a file or a secret on a seal.net page. The answer lands in a 0600 file.
seal pair [--name <name>] [--forget]Connect to your SEAL inbox once: a seal.net page with eight words to compare. After it every seal you send also shows in your inbox, --to owner sends straight there, and seal request can ask there. --forget disconnects.
seal inbox [--wait] · open <id> · rm <id>Files sent to this device’s address: list them (--wait waits for one), open one like receive, or take one out.
seal run --seal <url>|--item <id>[=NAME] --redact -- <cmd>Open a text secret from a link or an inbox item into a program’s environment, wipe the file, then run the program; --redact takes the value out of its output.
seal doctor [--transcripts] [--path <dir>]Look into this machine only: where the key comes from; --transcripts finds keys and SEAL links leaked into agent transcripts and shows them masked.
seal listSeals created from this machine.
seal status <id>Live backend state: active, expired or revoked.
seal files <id>Per-file listing for a seal.
seal append <id> <files…>Add files to an existing seal you own.
seal share mint <id>Mint an additional share link (optionally for a subset of files).
seal share list <id>List share links for a seal.
seal share revoke <id> <code>Kill one share link, keep the seal.
seal import <manage-url>Adopt a seal created in another client.
seal keygenPrint this machine’s address and eight words: senders seal links to it, and only the key on this machine opens them.
seal revoke <id>Revoke the whole seal. Recipients get “Seal Revoked”.
seal updateUpdate the CLI to the latest release: it downloads the archive from seal.net, checks its SHA-256 sum and replaces this binary; a CLI installed with Homebrew prints brew upgrade seal-hq/tap/seal instead.

Access rules are flags on seal send: TTL (--ttl 5m|30m|1h|1d|7d), password, single-use, max opens, geo allowlist, NDA, and --tier above 1 GB. Every command takes --json: one JSON object on stdout, and the exit code names the failure (2 input, 3 network, 4 server, 5 access, 6 payment, 7 client outdated: seal update). --message (or --message-file) adds a note to the recipient, encrypted inside the seal.

Scripting

# CI artifact handoff: seal the build, post the link
url=$(seal send build.tar.gz --ttl 1d --json | jq -r .share_url)
notify-team "$url"

# A secret from a link, straight into the program's environment
seal run --seal "$KEY_LINK=OPENAI_API_KEY" -- ./deploy.sh

The CLI keeps its state in a local config dir (override with SEAL_CONFIG_DIR); its key can come from SEAL_SEED instead of the file, so a CI job keeps one address across runs.