Rift: Better Alternative to Git Worktrees

f4n4tiX 51 points 26 comments June 01, 2026
github.com · View on Hacker News

Discussion Highlights (15 comments)

pikdum

Neat! Would a similar approach work with ZFS instead of btrfs?

ramon156

Readme seems generated then minimized to the extreme, to a point where I cannot follow it anymore. > The JavaScript init function initializes exactly `at`; Git-root selection and `--here` are CLI behavior. What does this mean? Maybe I'm missing something Also some of the stuff in this README seems like it should be in comments above/in their respected code blocks. It also did not tell me why rift is a better alternative. Because it's fast? git worktrees are also fast.

rippeltippel

I find it hard to understand what it is about. Better in what way?

singiamtel

Will this replace /warp in Opencode? Seeing as it's made by the same team

luckymate

If that achieves quick COW copies of whole repo and works on Mac OS that's the solution I've been looking for last few weeks. Internets and Claude were insisting that such copies are possible only on Linux via OverlayFS. Seamless switching between unrelated features in the same repo – here I come!

rubnogueira

Does it work well when we have gitsubmodules? I had some issues regarding that.

sbinnee

Is it just an experimental tool by opencode team? If there is some article about this tool, I would love to read it. It’s not clear to me why I should use this instead of git worktree.

throwwwll

Brought to you by the infamous author of yet another llm harness - will exfiltrate all your data, then feign ignorance: https://github.com/anomalyco/opencode/issues/10416

pure-orange

Currently it just sounds like an alternative to work trees, but with no explanation on how it’s better. Seems early stages, use of btrfs is cool, but unsure why I’d use this right now

zjy71055

git worktree (or any COW snapshot like this) still leaves you reinstalling node_modules per tree and fighting over a dev server port. That's the actual cost, and none of these tools touch it. So I gave up on parallelizing inside one repo. I run agents across different projects — one repo each — and stay serial within a single project.

lanycrost

Don't see the real reason to use this, as well as readme file is too short and give no actual info what is the better versus existing tools. Can be called Yet another :D ...

thdxr

this is a 1 day old vibe coded experiment where i'm exploring some ideas

jauntywundrkind

Love to see btrfs subvolumes getting used!! I spent some time & tokens starting to work on jujutsu support for opencode. Whose workspace support is so so good. I wonder if JJ does reflink-- maybe gonna go add that, as low hanging fruit.

apex_sloth

Could be good option for rust projects with huge compile artifacts. Saving space and rebuild time.

orf

I wrote something similar with go, but MacOS only. Creating a worktree became instant, but the bottleneck shifted from that to git needing to build its index. Claude code runs `git status` in the background, meaning any speed gains are instantly gone.

Semantic search powered by Rivestack pgvector
9,294 stories · 87,504 chunks indexed