vex

Parallel workstream manager. Create isolated workstreams (git worktree + tmux session) for each feature branch you're working on.

Install

# From crates.io
cargo install vex-cli

# With Nix (run directly)
nix run github:sandipndev/vex

# With Nix (in a flake)
# inputs.vex.url = "github:sandipndev/vex";
# then add: vex.packages.${system}.default
# or use the overlay: overlays = [vex.overlays.default]; -> pkgs.vex

# From source
cargo install --path .

# From GitHub releases
# Download binary from https://github.com/sandipndev/vex/releases

Quick Start

# Register a repo
cd ~/projects/my-app
vex init

# Start a new workstream — creates worktree + tmux session
vex new feature-auth

# Or open a GitHub PR directly
vex new '#42'

# List workstreams
vex list

# Re-attach to a workstream
vex attach feature-auth

# Clean up
vex rm feature-auth

How It Works

Each workstream is a git worktree + tmux session:

• Worktrees live at ~/.vex/worktrees/<repo>/<branch>/
• tmux sessions are named vex/<repo>/<branch>
• Default windows: nvim, claude, zsh
• on_create hooks run once when a workstream is created (default: direnv allow)

When you run vex new <branch>:

1. Fetches from origin
2. If the branch exists remotely, tracks it; otherwise creates it off the default branch
3. Creates a git worktree
4. Opens a tmux session with your configured windows

Configuration

vex config    # opens ~/.vex/config.yml in $EDITOR
vex reload    # validate and show current config

Default ~/.vex/config.yml:

windows:
  - name: nvim
    command: nvim
  - name: claude
    command: claude
  - name: zsh
    command: ''
hooks:
  on_create:
    - direnv allow

Commands

Use -r <repo> with new, attach, rm, list to target a repo from anywhere.

Environment

• VEX_HOME — override config/worktree root (default: ~/.vex)