Rift

Rift vs A2A

A2A is how agents from different vendors hand each other tasks. Rift is how they share files.

A2A

Youlaptop
work
api
billing
runs
.env
A protocol. It stores nothing. A file is sent as a copy or as a link.
one file in a message
OpenClawOpenClawanother company's agent
holds a credential for the other agent's scheme
report.pdfcopy

Rift

Youlaptop
work
api
billing
runs
.env
Rift Cloud
It cannot read your files. It holds only ciphertext.
Fv+a8LdicjU6ce
efFPD/W3GEGTbB
FFu91EY6OfuOIc
j3iz+iV3W5kvab
1hZDb7nJAxjHmy
one folder, read
OpenClawOpenClawanother company's agent
holds its own key
apiread

What A2A is

Agent2Agent is an open protocol for agents built by different vendors. An agent publishes a card that describes it, and other agents send it tasks, follow their progress and receive the results. It runs over ordinary HTTPS, so it fits behind an existing API gateway. Version 1.0 was released in March 2026.

How they differ

A2A defines the conversation between two agents and leaves authorization to each side. A file travels as a copy inside a message, or as a link to someone's storage. Rift keeps one set of files in sync and defines who can read them.

A2ARift
IdentityA2AA credential for whatever scheme the other agent's card declares.RiftA key that each machine and agent makes for itself. No account.
Smallest shareA2ANot defined. The specification leaves authorization to each implementation.RiftA folder, a subfolder or one file, as read or write.
Who checks accessA2AEach receiving server, by its own policy.RiftEach machine that receives a file checks the grant itself.
Who can read your filesA2ABoth ends, and anything between them that terminates TLS. We found no end-to-end encryption in the specification.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offA2ANothing moves unless the other agent's server is up.RiftFiles stored in Rift Cloud stay available.

Which to choose

Choose A2A when

  • Agents from different vendors need to delegate tasks to each other.
  • You want a standard task model over HTTPS.
  • Results are small enough to send in a message.

Choose Rift when

  • Two agents need to keep working on the same files.
  • The files are large or change often.
  • No gateway or proxy between the two agents should be able to read the files.

Using them together

One agent can hand another a task over A2A while both keep their files in Rift.

Use Rift with A2A

Based on the A2A specification, version 1.0.1, read in October 2026. Sources: specification, releases.

View as Markdown