Real Git worktrees
Branches, commits, hooks, and status remain owned by Git.
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.
curl -fsSL https://riftri.dev/install.sh | bashREPOSITORY / 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.
- 01Exact Git treea4d2c19
- 02Immutable basereuse or create
- 03Native copy-on-write view. APFS clone on macOS, Linux reflinks and mount-capable OverlayFS, and Windows ReFS block clones are current experimental backends.
- 04Linked worktreeclean + writable
GIT OWNS THE WORKTREE RIFTRI EXITS AFTER CREATION
Shared unchanged data
Native copy-on-write backends share unchanged data; edits stay private.
No filesystem proxy
Editors, builds, and agents read and write the native filesystem directly.
02MEASURED SAVINGS
Worktree disk usage
New disk allocation for ten assistant-ui worktrees, using the same tracked source in both comparisons.
APFS reference measurement · new volume allocation
- Ordinary Git10 full checkouts
- 774.01 MiB
- Riftri / APFS on macOS, native reflinks on Linux, and ReFS on Windows. The chart shows the APFS reference measurement.10 views + shared base
- 100.62 MiB
LESS NEW ALLOCATION87.0%
673.39 MiB saved
Includes the shared base and all ten views.Source files only on APFS. Dependencies and builds excluded.
Benchmark details
Creation time: Riftri 22.44 s · Git 9.90 s.
· adjusted assistant-ui snapshot (linguist-generated removed). Disk use measured at the volume level.
Backend names show support, not Linux or Windows measurements. Results vary.
Read full benchmark03QUICK 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.
- 01Install on macOS or Linux
Downloads the native CLI and verifies SHA-256. No Node.js required.
curl -fsSL https://riftri.dev/install.sh | bash - 02Check support
Doctor is read-only and explains blockers before anything changes.
riftri doctor --destination ../app-auth - 03Create 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 supports glibc and musl.