On your machine
Sanitize at the source
Relay’s skill selects the workspace or target skill and excludes secrets, unsafe paths, caches, dependencies, and other disposable data.
Private by default · public by choice
Save an entire agent workspace or one reusable skill as locally encrypted ciphertext, or deliberately publish a separately sanitized artifact for stable, anonymous, keyless restore. You choose the boundary.
Paste the prompt into your agent. Relay verifies the bundle before installation.
Open source on GitHub — audit, fork, or self-host RelayCreate a private Relay checkpoint of this workspace.
Agent
A deliberate visibility boundary
Every agent workspace or skill checkpoint is filtered and verified locally. Private artifacts remain encrypted; public artifacts are readable by design.
On your machine
Relay’s skill selects the workspace or target skill and excludes secrets, unsafe paths, caches, dependencies, and other disposable data.
Your choice
Private checkpoints are sealed locally with AES-256-GCM. Public checkpoints use no key and publish only the title, description, metadata, and files you explicitly approve.
Cryptographically checked
Private restore decrypts locally. Public restore needs no sign-in or key. Both paths reject unsafe paths and verify every file hash.
Private means private
A private archive is encrypted before it leaves your workspace. Publishing creates a separate readable artifact only after a local preview and explicit confirmation; it never uploads the original key.
A boundary you can see
Private mode sends an opaque .relay file plus approved or pseudonymous agent metadata. Public mode sends a separate sanitized archive plus the public title and description you approve. Anyone with its stable URL can read and restore it without a key.
Protect the next handoff
Install Relay, choose private or public, and restore with integrity verification.