SEAL

Give the user or another agent a file or a secret WITHOUT it passing through this chat. Works for large files (folders, dumps, exports, builds, videos — free up to a limit, more after one card payment by the user). Once the user's inbox is connected (seal_pair) the default mode is `inbox`: the file lands there and there is nothing to copy. Otherwise the default is `handoff`: the link goes to the user's clipboard and you get a handle. Where there is no clipboard it goes to a 0600 file and you get its path: do not read that file and do not print it. Mode `forward`: a link only the agent with the given SEAL address can open — use it for another agent. When the user is connected, every seal you create also appears in their inbox, where they can manage and revoke it. Never paste secrets or huge content into the chat instead.

Ask the user for a file or a secret (API key, token, password) WITHOUT them pasting it into the chat. They answer on a seal.net page: on their computer it opens in their browser by itself, elsewhere they get its link or a card in their inbox; you can pass `where_url` (the page where that key is created) so they find it in one click. With `wait:true` you get the path of the saved 0600 file, never the value. Use this instead of "paste your key here" or "upload the file here".

Connect this agent to the user's SEAL inbox, once. After that seal_share sends to the inbox by default and seal_request can ask there. The user compares three words on the page with the ones you show.

Open a SEAL link. `metadata` shows name, size and expiry without consuming a read. `file` streams the content to disk and returns the path — use it for large files, secrets and anything you pass to a program. `inline` returns small JSON/CSV/plain text into the conversation and refuses secrets and HTML/PDF.

What other agents or people sent to you: seals addressed to your SEAL address, no link needed. Returns handles; open one with seal_open item=<handle>. `wait`: seconds to wait for something new, 0 to 300.

Run a program with secrets from SEAL links or your inbox in its environment. The values never enter this conversation: they are removed from the output you get back. Use it instead of reading a secret file.

Seals you created through this server: opaque handles with status and expiry. Seals made with the CLI, the web or another client live elsewhere and are not listed.

Put the link of a handoff seal you made on the user's clipboard again (or in its 0600 file), by its handle: for a link that was lost before it reached the recipient. You never get the link itself. Seals of mode inbox are in the user's inbox, and forward links came back to you: neither has one here.

Revoke a seal you created, by its handle: the link stops working and the ciphertext is deleted. Idempotent: an already revoked or expired handle returns {revoked:true}.