00OPEN SOURCE / BUILT FOR PARALLEL WORK

Riftri

LIGHTWEIGHT GIT WORKSPACES FOR PARALLEL DEVELOPMENT_

Real, isolated Git worktrees that share the unchanged parts of your project. Keep using normal files, normal Git, and the tools you already have.

Install on macOS or Linux (glibc)

curl -fsSL https://riftri.vercel.app/install.sh | bash
[ LIVE WORKTREE MAP ]
REPOSITORY / EXACT TREEa4d2c19
00
immutable baseone materialized Git tree / read only
01
auth/feature/auth
02
billing/feature/billing
03
tests/fix/worktree-tests
· shared block private edit
01STORAGE MODEL

How Riftri stores linked worktrees

Riftri changes how worktree files are created and stored. It does not replace Git, manage branches, or sit between your tools and the filesystem.

[ FROM TREE TO WORKSPACE ]
  1. 01Exact Git treea4d2c19
  2. 02Immutable basereuse or create
  3. 03Native copy-on-write view. APFS clone on macOS, Linux reflinks and mount-capable OverlayFS, and Windows ReFS block clones are current experimental backends.
  4. 04Linked worktreeclean + writable
GIT OWNS THE WORKTREE RIFTRI EXITS AFTER CREATION
01

Real Git worktrees

Branches, commits, hooks, and status remain owned by Git.

02

Shared unchanged data

Native copy-on-write backends share unchanged data; edits stay private.

03

No filesystem proxy

Editors, builds, and agents read and write the native filesystem directly.

02QUICK START

Create a Riftri worktree

Install the CLI, then run the support check from a Git repository. Riftri stops unless a supported native storage backend is available.

  1. 01
    Install on macOS or Linux

    Downloads the native CLI and verifies SHA-256. No Node.js required.

    curl -fsSL https://riftri.vercel.app/install.sh | bash
  2. 02
    Check support

    Doctor is read-only and explains blockers before anything changes.

    riftri doctor --destination ../app-auth
  3. 03
    Create a worktree

    Start with the explicit, debuggable interface.

    riftri worktree add ../app-auth -b feature/auth main

Installs to ~/.local/bin. Follow the printed PATH command before step 02. Shell profiles and Git activation stay unchanged. Linux requires glibc.