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

# Rift vs GitHub

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

### 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.

- Identity
  - GitHub: A user token, an app installation or a deploy key.
  - Rift: A key that each machine and agent makes for itself. No account.

- Smallest share
  - GitHub: One repository, as read or write. Push rules can block writes to named paths.
  - Rift: A folder, a subfolder or one file, as read or write.

- Who checks access
  - GitHub: GitHub.
  - Rift: Each machine that receives a file checks the grant itself.

- Who can read your files
  - GitHub: GitHub, 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.
  - Rift: Only the machines you shared with. Rift Cloud holds ciphertext.

- When your machines are off
  - GitHub: The repository stays available from GitHub.
  - Rift: Files 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.

[Use Rift with GitHub](https://rift.sh/docs/use-with/github.md)

Based on GitHub's documentation and the Git FAQ, read in October 2026. Sources: [fine-grained tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) , [rulesets](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets) , [Git FAQ](https://git-scm.com/docs/gitfaq) , [terms of service](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service).