Rift vs GitHub

GitHub moves the files Git tracks, one repository at a time. Rift moves every file in a folder.

GitHub

Youlaptop
work
api
billing
runs
.env
GitHub
It can read your files.
work
api
billing
one repository
OpenClawOpenClawanother company's agent
holds a repository token
work
api
billing

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 GitHub is

GitHub hosts Git repositories, and most coding agents get their files by cloning one. A token can be limited to specific repositories, and every change has history and review.

How they differ

We found no way to limit reads below the repository, so an agent that needs one folder receives the whole repository. Files that Git does not track, such as build output, reports and local configuration, do not travel. Rift shares a single folder and carries everything in it.

GitHubRift
IdentityGitHubA user token, an app installation or a deploy key.RiftA key that each machine and agent makes for itself. No account.
Smallest shareGitHubOne repository, as read or write. Push rules can block writes to named paths.RiftA folder, a subfolder or one file, as read or write.
Who checks accessGitHubGitHub.RiftEach machine that receives a file checks the grant itself.
Who can read your filesGitHubGitHub, and everyone with read access to the repository. Its terms say staff do not open private repositories without consent, except for security, automated scanning, a support request from the owner, the integrity of the service, or a legal obligation.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offGitHubThe repository stays available from GitHub.RiftFiles stored in Rift Cloud stay available.

Which to choose

Choose GitHub when

  • The work is code and you want history, branches and review.
  • Your team already works in pull requests.
  • Everything that matters is committed.

Choose Rift when

  • Agents produce files that do not belong in a repository.
  • An agent should receive one folder out of a larger project, with no separate repository made for it.
  • Build output and reports should be on every machine.

Using them together

Git holds the source and its history. Rift carries what Git leaves behind, such as reports, datasets, screenshots and video. Git's FAQ says not to use a cloud syncing service on any part of a repository, and that applies to Rift too.

Based on GitHub's documentation and the Git FAQ, read in October 2026. Sources: fine-grained tokens, rulesets, Git FAQ, terms of service.