> Documentation index: https://rift.sh/llms.txt

# The universal filesystem for agents.

Agents write reports, code and video on many machines. Rift is the encrypted filesystem where they store and share them.

[Install](https://rift.sh/docs.md#install) [What is Rift?](https://rift.sh/docs/what-is-rift.md)

## Every machine and agent makes its own key.

That key is its identity. There is no account and no password.

## The same folders on all your machines.

Every run writes into a folder you own, and that folder syncs to all your machines.

## Each agent sees only its folders.

Share a folder with an agent, as read or write. The agent receives that folder and nothing else.

```
$ rift share runs/codex-484 codex
```

## Machine to machine at gigabit speed.

Files stream directly between machines. A relay carries them when there is no direct path.

## Offload massive files to Rift Cloud.

A large file moves off the machine that wrote it and downloads when it is opened. Everything in Rift Cloud is ciphertext.

## Output outlives the sandbox.

Files reach your machines as the run writes them, and they stay after the sandbox is gone.

## Agents ask each other for files.

One agent asks in plain words. The other sends a file it is allowed to share.

```
$ rift ask hermes "the latest report"
```

## An offline agent's files still arrive.

The file comes from another machine that has it, or from Rift Cloud.

## Approve access from any machine.

An agent requests a folder and says why. You approve or decline.

```
$ rift approve 3
```

## Remove access and the updates stop.

The agent keeps running. Nothing you write afterwards reaches it.

## Remove an agent entirely.

Everything it could read gets a new key. It keeps what it already downloaded and can open nothing newer.

## Built for any agent that has a shell.

An agent reads and writes ordinary files and runs `rift` from its shell. There is no plugin to install.

- Claude Code
- Codex
- Hermes
- OpenClaw
- Cursor
- OpenCode
- Grok Bot
- Buzz
- Claude Tag

## Start with one prompt.

Paste one prompt into the agent. It installs Rift, joins your filesystem and keeps its work there.

1.Create an invite

You

MacBook Pro

```
$ rift invite claude-code
✓ invite for claude-code rift_4f1c…9a2e
```

2.Put the token in the prompt and paste it into the agent

Prompt

for the agent

```
Run rift status first. If the command is not found, run ~/.local/bin/rift status.
If it shows a key that starts ed25519: and no "joined as", this machine already uses my key. Stop and ask me before you use the token.
If it shows "joined as", Rift is set up here. Skip the install and the join below.
Install Rift: curl -fsSL https://rift.sh/install | sh
Then run: rift init --invite <token>
Work inside the folders that rift ls shows. Everything in them is an ordinary file.
If you need a folder you cannot see, run:
    rift request <path> --reason "<why>"
To get a file from another agent, run:
    rift ask <agent> "<what you need>"
Full steps, and when to stop and ask: https://rift.sh/setup.md
```

3.The agent joins

Claude Code

sandbox

```
$ curl -fsSL https://rift.sh/install | sh
✓ installed rift 0.1.0 to ~/.local/bin
$ rift init --invite rift_4f1c…9a2e
✓ created a key for this machine
  ed25519:53259d49…2919e7
✓ joined as claude-code
✓ folder at ~/rift
```

## Share a folder in one command.

Approving a request and removing access take one command each, from any of your machines.

[All commands](https://rift.sh/docs/commands.md)

You

MacBook Pro

```
$ rift share runs/codex-484 codex
✓ shared runs/codex-484 with codex · write
$ rift requests
  3  codex  read  work  "To re-run the tests with your fix"
$ rift approve 3
✓ shared work with codex · read
$ rift unshare work codex
✓ removed codex from work · new key
```

## Private by default.

We cannot read your files, and neither can the machines that store or carry them. A removed agent keeps only what it already downloaded.

[Security](https://rift.sh/security.md)

### You

Read and write everything, on all your machines.

### An agent

Reads or writes only the folders you shared with it.

### Rift Cloud

Stores ciphertext. It sees no file names and no contents.

### A relay

Carries ciphertext between two machines. It cannot read it.

### Rift, the company

Holds none of your keys. Anything it handles for you is ciphertext.

## From agents to superintelligence.

Agents are taking over knowledge work, and no one company runs them. They run across heterogeneous machines, clouds and owners, and so will whatever follows them. The knowledge they generate has to be stored and shared across all three.

Rift combines CRDTs, group key agreement and peer-to-peer over QUIC, so that private, shared state can cross machines, clouds and owners.

[About Rift](https://rift.sh/company.md)

## How Rift compares.

Shared disks and sandboxes give agents fast files inside one company's account. Rift is for files that cross machines, clouds and owners.

- [Archil](https://rift.sh/compare/rift-vs-archil.md): Agent storage
- [E2B](https://rift.sh/compare/rift-vs-e2b.md): Sandboxes
- [Claude Managed Agents](https://rift.sh/compare/rift-vs-claude-managed-agents.md): Hosted agents
- [Letta](https://rift.sh/compare/rift-vs-letta.md): Agent memory and state
- [MCP](https://rift.sh/compare/rift-vs-mcp.md): Protocols
- [Syncthing](https://rift.sh/compare/rift-vs-syncthing.md): Sync and storage
- [All comparisons](https://rift.sh/compare.md): 28 products and protocols

## Put your agents on one filesystem.

[Install](https://rift.sh/docs.md#install) [Read the docs](https://rift.sh/docs.md)