grove

README

Grove (gw)

grove /ɡrōv/ noun — a small group of trees growing together.

Why?

Monorepos solve cross-project work, but not everyone has one. You've got separate repos, separate CI, separate deploys — and that's fine until you need to work across them.

One feature across three services means git worktree add three times, tracking three branches, jumping between three directories, cleaning up three worktrees when you're done. It's annoying.

Grove gives you the multi-repo worktree workflow that monorepos get for free. One command, one workspace, all repos on the same branch.

Install

Homebrew

brew install nicksenap/grove/grove

Go install

go install github.com/nicksenap/grove/cmd/gw@latest

From source

git clone https://github.com/nicksenap/grove.git
cd grove && go build -o gw ./cmd/gw
mv gw /usr/local/bin/

Upgrading

brew update && brew upgrade grove

Then add shell integration:

Bash / Zsh — add to .zshrc or .bashrc:

eval "$(gw shell-init)"

Nushell — generate and source the init file:

gw shell-init --shell nu | save -f ~/.config/nushell/grove.nu
# then add to config.nu:
source grove.nu

This enables gw go to change your working directory and auto-cds into new workspaces after gw create.

Usage

# Register your repo directories (one-time)
gw init ~/dev ~/work/microservices

# Create a workspace: name the branch, pull repos from a preset or a list
gw create -b feat/login -p backend        # repos from a saved preset
gw create -b feat/login -r svc-a,svc-b    # …or an ad-hoc repo list

# Work across the whole workspace
gw go my-feature       # cd into the workspace
gw status my-feature   # git status across every repo
gw sync my-feature     # rebase all repos onto their base branch
gw run my-feature      # run dev processes (TUI)

# Clean up when done
gw delete my-feature   # removes worktrees + branches

Interactive menus support type-to-search filtering, arrow-key navigation (single-select), or arrow + tab (multi-select) with an (all) shortcut.

Presets, plugins, hooks, and the full command reference are covered in Workflows and Operations.

Documentation

Full documentation lives in the OpenWiki — start with the quickstart, then dive into the area you need:

• Quickstart — install, first commands, key concepts, and a source map
• Architecture — layered design, data model, concurrency, and key decisions
• Workflows — how each command maps to code (create, sync, run, delete, presets…)
• Operations — configuration, hooks, state, troubleshooting, and release process
• Integrations — plugins, the MCP server, and workspace source provenance

Focused topic guides

• Hooks — global hooks (terminal integration) & per-repo hooks (.grove.toml, gw run)
• Plugins — extend gw with external commands
• AI coding tools — Claude Code workflows, MCP server

Requirements

No dependencies — single static binary. Requires git on PATH.