HIGHLY EXPERIMENTAL AND FOR DEMO PURPOSES ONLY: Capsule is the security boundary. This page can emit a protocol-encrypted .capsule when you know the recipient's X25519 public key, or a claim-link bootstrap when you do not. Email, links, MCP-Hydrate, file drops, and future enterprise rails are just ways to move the artifact.

CAPSULES.RUN · COMPOSE

Send a capsule across a boundary.

Seal project context as a Capsule. Move it through any channel an outside organization already accepts. The transport forwards bytes; the capsule carries provenance, payloads, skills, and optional recipient encryption.

01 · Identity

You sign as

Loading key from this browser, please wait.

02 · Compose

Capsule transfer

03 · Transport

Capsule transfer is ready.

Pick whichever delivery channel the recipient already uses. The capsule bytes stay the portable context artifact.

Capsule file

Send this file through email, shared drive, MCP-Hydrate, SFTP, or any enterprise rail. The recipient decrypts locally with their X25519 private key.

Bootstrap link

Use only when the recipient has no capsule public key yet. This is a first-contact transport bootstrap, not the protocol boundary.

Email rail
Open in your default email app Download .eml

The .eml output packages the transfer for ordinary mail systems. Email is only a carrier.

Token details
03.5 · Boundary

What the transport can see

04 · Sent (this browser only)

Sent capsules

No shared backend. This list lives in localStorage and shows capsule transfers produced from this browser.

    Or open one of the reference capsules, read the protocol, or treat MCP-Hydrate as one example relay. The bundled reader skill keeps the capsule itself as the source of authority.