SEAL Box: a browser inbox for files from your AI agent

I'm Maria, working on SEAL.

When an agent produces a report or another file, you still need a practical way to receive it. SEAL Box provides a browser inbox for agent-generated files. You can also respond to file requests in your browser, without pasting the file contents into chat.

SEAL's web transfer encrypts files in the browser before upload. The basic sharing flow does not require an account or email. You can set expiry and password protection, use single-use access, and revoke future access. Revocation does not remove copies someone has already downloaded.

For agent workflows, we provide MCP and CLI tools. Our published Claude Code skill guides an agent in using those tools for delivery, inboxes, requests and revocation. The skill is guidance, not a separate transfer service.

Two practical details: save your Box recovery key privately, and review your agent host's permissions. A file path is not a security boundary if the agent can read that file.

Try Box: https://box.seal.net/
MCP setup: https://seal.net/docs/mcp
Official plugin and skill: https://github.com/seal-hq/claude-plugins

If you work with agent-generated reports, what is missing from your current delivery workflow? I'd value feedback on the handoff and inbox experience.

A simpler route when the finished report is already on your laptop: you don't need Box or an MCP setup just to send it to someone. I work on SEAL; here's the ordinary browser flow.

1. Open https://seal.net and choose Tap to send.
2. Select your PDF or ZIP, choose how long the link should work, and create the transfer.
3. Send the recipient link in your existing email or chat. Neither person needs a SEAL account. Keep the separate management link private.

The free option supports up to 1 GB per transfer and up to 7 days. If several colleagues need the file, don't choose single-use access. For a password-protected handoff, send the password through a separate channel.

This is temporary delivery, not a permanent archive. Expiry or revocation stops future access through the link; it cannot remove a copy someone has already downloaded.

An update for people whose finished report is in a terminal or agent workspace: SEAL also has a CLI for macOS and Linux. This is a documented option, rather than a new release announcement.

After setup, a simple handoff is:
seal send report.pdf --ttl 1d

The CLI encrypts locally before upload. Share the recipient link and keep the separate management link private. The machine running the command must actually have access to the file; a path inside a different browser VM will not become accessible just because you paste it into an agent.

CLI setup and commands:

For a first check, send a small non-confidential report to a colleague and ask whether they could download and open it. The free allowance is 1 GB total per transfer for up to 7 days. Keep your original: expiry cannot erase a copy already downloaded.

Which step causes friction in your workflow: locating the generated file, delivering it, or opening it on the receiving device?

I help with SEAL outreach; this update was written with AI assistance. The example follows our documentation and is not a claim that we tested your agent host.