Introducing Rift
Rift is the universal filesystem for agents. Everything your agents write is in one place you own, and each agent sees only the folders you share with it.
Today we are releasing Rift for macOS and Linux. We work on one question: how do agents store and share the knowledge they generate? Rift is our answer so far.
Agents work across machines, clouds and owners
Agents are taking over knowledge work. They write code, reports, datasets, plans, screenshots and video.
We are moving toward superintelligence, and no one company will run it. Agents already run on a laptop, on a Mac mini at home, in a sandbox that lasts an hour and on several clouds at once.
They also work for more than one owner. Your own agent works beside a vendor's, and one company's agent hands a file to another company's. The knowledge has to cross from one owner to another.
Storage was built for one owner
An agent's files usually go in a bucket in one company's object storage account. Another company's agent gets in only when that account's owner lets it in.
Agents work better with files than with objects, and companies such as Archil now give an agent a fast disk on top of object storage.
The disk still belongs to one account. Work that two companies share sits in one company's account.
One filesystem for every agent
Rift gives all your agents one filesystem, on any machine or cloud. It belongs to you, and it is not tied to one company's storage account.
An agent reads and writes ordinary files, and what it writes appears on every machine that has been given access.
There is no account and no password. Each machine and agent makes its own key the first time it runs Rift, and that key is its identity.
You share a folder with an agent, as read or write. Here a Codex sandbox gets the folder for its run and sees nothing else of yours.
$ rift share runs/codex-484 codex✓ shared runs/codex-484 with codex · write
Files reach your machines as the run writes them, and they stay after the sandbox is gone.
An agent that needs another folder asks for it and says why. You approve or decline from any of your machines.
Sharing with an agent that belongs to another person or company works the same way as sharing with your own. You share a folder with the key of Sam's agent, OpenClaw, and it appears on OpenClaw's machine. Neither of you opens a storage account to the other.
You can remove an agent from a folder at any time with rift unshare. The folder gets a new key, and nothing written afterwards opens with the old one.
Private by default
We cannot read your files, and neither can the machines that store or carry them. Files are encrypted before they leave the machine, and they move directly from one machine to another.
Rift Cloud is optional storage, and the one part of Rift that needs an account. It keeps an encrypted copy for when your machines are off, and it holds only ciphertext.
How Rift is built
Rift is built on recent work in three fields, the way agents are built on recent work in language models.
| Field | What it gives you |
|---|---|
| CRDTs | Two machines can change the same folder at the same time, online or off. Their changes merge on their own, and no server decides which came first. |
| Group key agreement | The machines and agents a folder is shared with agree on its key among themselves. When one is removed, the rest agree on a new key. |
| Peer-to-peer over QUIC | Machines connect to each other directly across networks. When they cannot, a relay carries the ciphertext. |
The libraries are Automerge for CRDTs, Keyhive for group key agreement and iroh for peer-to-peer over QUIC. Rift Cloud keeps its ciphertext on Sia.
The six jobs of file sync covers the systems that came before.
Limits
Rift does not run on Windows.
It has not had an independent security audit.
Agents that run as the same user on one machine can read each other's files.
Removing access cannot take back a file a machine already downloaded. After you remove an agent from a folder, replace any secret that was in it.
Machines still need servers to find each other, and a relay to carry files when there is no direct path. Neither can read the files.
Start with one prompt
Install Rift on your machine, create your key and make an invite. Put its token in the prompt and paste the prompt into your agent. The agent installs Rift, joins your filesystem and keeps its work there.
$ rift invite claude-code✓ invite for claude-code rift_4f1c…9a2e
The docs cover every command, and the security page lists what is and is not protected.
Agents are the first users of Rift. Whatever follows them will also need to store and share the knowledge it generates. Come build this with us.
Written from Archil's pages on sharing disks and security, read in October 2026.