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.
It's a ~1d old experiment. Not sure why posted on hackernews.
Rift: Better Alternative to Git Worktrees
21–30 of 32 posts
Re: Rift: Better Alternative to Git Worktrees
#22git 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.
Re: Rift: Better Alternative to Git Worktrees
#23git 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.
This! A hundred times over. It's hard enough having to review one serial set of changes managing parallel changes into a single code base has been a nightmare load on my brain so I avoid that unless I'm trying to prototype something quick and dirty.
Re: Rift: Better Alternative to Git Worktrees
#24Don'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 ...
Re: Rift: Better Alternative to Git Worktrees
#25this is a 1 day old vibe coded experiment where i'm exploring some ideas
Re: Rift: Better Alternative to Git Worktrees
#26Love 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.
Re: Rift: Better Alternative to Git Worktrees
#27Could be good option for rust projects with huge compile artifacts. Saving space and rebuild time.
Re: Rift: Better Alternative to Git Worktrees
#28I 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.
Re: Rift: Better Alternative to Git Worktrees
#29Brought 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
Search issues for "privacy" and some very worrying discussions are there.
Include closed issues, as some have been closed without resolution.
Re: Rift: Better Alternative to Git Worktrees
#30git 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.
you are right, I've experimented with cp -a on macOS as well for https://github.com/madarco/agentbox and in the end found it's actually faster to use worktrees inside docker containers while mounting your .git repo inside them.
Then after the node_modules (or apt packages) are installed, take a docker commit snapshot.
Now I have truly isolated parallel workspaces in Also the system was easy to adapt to cloud environments as well so now I have Hetzner, Vercel, Daytona as well (using their native snapshotting systems for fast boot after the initial setup)