No reviews yetBe the first to leave a review for Rift
Framer — Launch websites with enterprise needs at startup speeds.
Launch websites with enterprise needs at startup speeds.
Promoted
Maker
📌
Hey everyone! I'm Priyash, the maker of Rift.
I built Rift because I kept running into the same problem: I'd be working with an AI coding agent on one feature, and while waiting, I'd want to start another task - but my repo was already dirty. Stashing, switching branches, re-installing deps... it killed the momentum.
Rift fixes this with git worktrees. One command - rift open - creates an isolated branch and worktree, runs your setup hooks, and drops you in with your AI agent already running. Each worktree is completely independent, so you can have 5 features in progress at once with zero conflicts.
What makes it different:
Agent-agnostic - Works with Claude Code, Copilot, Codex, Aider, or literally any CLI command
Zero config to start - npm install -g @priyashpatil/rift, then rift init in your project
No port collisions - Deterministic hash-based port mapping so every worktree can run dev servers simultaneously
One workspace view - rift code opens all active worktrees in a single VS Code/Cursor/Windsurf workspace
It's open source, MIT licensed, and built with Bun. Fun fact - Rift itself was built entirely with Claude Code. Would love your feedback - happy to answer any questions!
Yooo I'm from web3 too! Glad to see you here! I've been shipping a product entirely through Claude Code on a single VPS, and the dirty repo problem is real. More than once I've had Claude halfway through a refactor when I realized I needed to hotfix something on main. My "solution" was just opening another SSH session and praying nothing conflicted haha. Not great.
Hey everyone! I'm Priyash, the maker of Rift.
I built Rift because I kept running into the same problem: I'd be working with an AI coding agent on one feature, and while waiting, I'd want to start another task - but my repo was already dirty. Stashing, switching branches, re-installing deps... it killed the momentum.
Rift fixes this with git worktrees. One command - rift open - creates an isolated branch and worktree, runs your setup hooks, and drops you in with your AI agent already running. Each worktree is completely independent, so you can have 5 features in progress at once with zero conflicts.
What makes it different:
Agent-agnostic - Works with Claude Code, Copilot, Codex, Aider, or literally any CLI command
Zero config to start - npm install -g @priyashpatil/rift, then rift init in your project
No port collisions - Deterministic hash-based port mapping so every worktree can run dev servers simultaneously
Lifecycle hooks - Auto-install deps, seed databases, assign ports - all triggered automatically
One workspace view - rift code opens all active worktrees in a single VS Code/Cursor/Windsurf workspace
It's open source, MIT licensed, and built with Bun. Fun fact - Rift itself was built entirely with Claude Code. Would love your feedback - happy to answer any questions!
GitHub: https://github.com/priyashpatil/rift
Docs: https://rift.priyashpatil.com
Yooo I'm from web3 too! Glad to see you here! I've been shipping a product entirely through Claude Code on a single VPS, and the dirty repo problem is real. More than once I've had Claude halfway through a refactor when I realized I needed to hotfix something on main. My "solution" was just opening another SSH session and praying nothing conflicted haha. Not great.
beehiiv
Congratulations on the launch @priyashpatil ! Look forward to checking how builders use this
Thanks @geetika_mehta