AI agent file transfer
Files in and out of agents, outside the chat.
Agent to person, person to agent, agent to agent. Free up to 1 GB per seal.
npx -y sealnet-mcp@latestMCP server · CLI · SDK · Python
Output that does not fit in a chat.
When a cloud agent wants to build a dump, or a report, or a video, there is no good way to hand it to a person. Chat conversations are too small for that. Cloud storage requires users to sign in.
When a person gives an agent a large file or folder, they do the reverse of what an agent does: they upload the files to some cloud drive first, and send the server a url.
What we need is a way for AIs and humans to send one another big files either way, without the agents having to acquire user accounts, and without the files getting read by a cloud service provider. That’s what SEAL does. In all cases, the encryption is done on the sending device, and no user account is required on either end.
It lands in your SEAL inbox or on your clipboard; the model sees a handle.
A seal.net page; the file lands on disk.
Sealed to one address and useless to anyone else.
Three flows, one tool set.
Install
npx -y sealnet-mcp@latest, or the seal CLI for agents with a shell.
Hand over
seal_share sends it to the person’s inbox or clipboard, never into the chat.
Ask
seal_request or seal request: the person answers on a seal.net page.
Forward
seal send --to with the other agent’s address from seal keygen.
From an agent to a person.
An agent with the SEAL MCP server sends a file with a single tool call. Connect it to your SEAL inbox once, with seal_pair, and every file goes there: nothing to copy, no link in the chat, no file left on the machine the agent runs on. Before that, on the person’s computer the link goes to the system clipboard; where there is none, it becomes a private file on the agent’s machine.
The model sees only a short handle for the seal and a receipt. The link and its key are deliberately omitted from the conversation. If the conversation is leaked, the user will still be protected.
The user opens the file from the inbox, where every seal the agent made waits with its page and a revoke button, or from the SEAL link on seal.net, with no account. Optionally the seal can be made to “burn” after one download, so that the link will be invalid once they’ve retrieved their file.
From a person to an agent.
When an agent needs a large file from the user, SEAL gives it the tools it needs for that too. The file the user chooses lands in a private folder on their hard drive. The agent sees its name and size, and their paths get put into the conversation instead of the actual contents of the file.
Sending an entire folder is special. The CLI and the MCP server bundle all its files into one ZIP archive, send it in streaming mode, and write it straight to disk rather than bringing the whole thing into memory.
From one agent to another.
An agent can seal a file not just for a person, but for another agent, by addressing the link to that agent’s address. The receiving agent prints its address and eight words with “seal keygen” and then opens the SEAL link, writing the file straight to disk.
Even if a link addressed to one agent gets leaked, it’s safe because the key to unseal it is wrapped for one recipient. Only the agent with the corresponding private key will be able to open it.
Size and payment.
A single seal can contain multiple files of different sizes, but there is a limit to their combined total size. A free seal can be up to 1 GB, but an individual file can be as large as 10 GB.
To send a file too large for a free seal, just make a single payment through the web interface. You’ll still only need a single link: as the upload continues, the sealed data will go directly into the same seal. No second seal, and no new link to give to people.
Questions, answered.
- How big can a file be?
- A free seal holds up to 1 GB and one file can be up to 10 GB. Above that, a person pays once and the upload continues into the same seal.
- Can the agent pay?
- No. The agent shows the payment link; a person pays by card or wallet on seal.net, and the upload goes on by itself.
- What does the model see?
- With your inbox connected, a handle and the eight words of your inbox; the file goes to the inbox. In handoff mode, a short handle and a receipt: the link goes to your clipboard, or to a private file on the agent’s machine whose path the receipt names.
- Which agents can use it?
- Any MCP host, such as Claude, Cursor or Cline, through sealnet-mcp, and any agent with a shell through the seal CLI, the TypeScript SDK or the Python package.
npx -y sealnet-mcp@latestMCP server · CLI · SDK · Python
One seal. Every platform.