Git worktree manager for AI agents

Spin up isolated worktrees, each with its own branch and AI coding agent, so you can work on multiple features at once without stashing or switching.

$ npm install -g @priyashpatil/rift

Run rift config, restart your terminal, then rift init in your project. See the Getting Started guide.

Rift - Git worktree manager for AI agents | Product Hunt

Features

Work on everything at once

Every task gets its own isolated worktree and branch, so you never stash, switch, or wait again.

Bring any agent

Claude Code, Copilot, Codex, Aider, or any CLI command — just plug it in.

Zero port conflicts

Deterministic hash-based port mapping means every worktree runs services simultaneously without collisions.

Hooks that handle the busywork

Auto-install deps, seed databases, assign ports — all triggered by worktree lifecycle events.

One workspace, all worktrees

rift code opens every active worktree in a single VS Code, Cursor*, or Windsurf workspace.

Launch and go

rift open creates the branch, sets up the worktree, and drops you in with your agent running.

Supported editors

VS Code, Cursor*, and Windsurf. All three support managed workspaces — rift code creates a .code-workspace file that includes all active worktrees.

*Cursor is a VS Code fork and supports .code-workspace files, but has known rough edges — particularly around file association on macOS and multi-root workspace context for AI features.

JetBrains IDEs and Zed have multi-root workspace support that is either in early stages or only partially implemented. Rift does not have built-in support for these editors at the moment. You can still use them by setting a custom editor command in rift.yaml, but rift code won’t manage a shared workspace file for them.

Supported agents

Any CLI agent works — just set the command in rift.yaml. Common agents include Amp, Claude Code, Codex, Continue, Copilot, Gemini, Kiro, and OpenCode, but you can use any command (e.g. aider, claude --model opus, or a custom script).