nicksenap/grove
nicksenap/grove has 100 GitHub stars and 13 forks. GitHot measured +1 stars in 24 hours, +3 in 7 days, and +5 in 15 days. Last checked 2026-11-17 03:08 UTC. Last push 2026-11-14.
Measured star growth
- in 24h
- +1
- in 7 days
- +3
- in 15 days
- +5
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Git worktree workspace orchestrator. One command creates a workspace folder with worktrees from multiple repos on the same branch.
Developer ToolsREADME.md
Original
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 creates a workspace with every repo on the same branch, and gw status shows all of them in one table.
Getting Started
Grove is a single static binary with no dependencies. It requires git on PATH.
1. Install Grove
Pick any one of the following methods:
Homebrew (macOS / Linux)
brew install nicksenap/grove/grove
Install script (macOS / Linux, no Homebrew needed)
curl -fsSL https://raw.githubusercontent.com/nicksenap/grove/master/scripts/install.sh | sh
Verifies the release checksum and installs to /usr/local/bin (or ~/.local/bin if that is not writable). Override with GW_INSTALL_DIR and GW_VERSION.
Go install (if you already have a Go toolchain)
go install github.com/nicksenap/grove/cmd/gw@latest
2. Add shell integration
This enables gw go to change your working directory and auto-cds into new workspaces after gw create.
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
3. Create your first workspace
gw init ~/dev # register the directory that holds your repos
gw create -b feat/login -r svc-a,svc-b # create the feat-login workspace across both repos
gw status feat-login # see every repo's branch and git status in one table
Let your coding agent drive it
Grove ships an agent skill that teaches Claude Code, Codex, Cursor, pi, and other skill-aware agents to set up Grove and run gw safely: explicit flags instead of pickers, JSON output, and which commands destroy work.
npx skills add nicksenap/grove --skill grove
No skills installer? Paste this prompt into your agent instead:
Read https://raw.githubusercontent.com/nicksenap/grove/master/skills/grove/SKILL.md and set up Grove for me.
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 reset my-feature # switch every repo back to the workspace branch, then sync
# Clean up when done (destructive; use a pre_delete hook to enforce policy)
gw delete my-feature # removes worktrees, branches, and workspace files
gw prune # list workspaces older than 7 days, plus stale records whose directory is gone
gw prune --yes # delete them (same two-phase cleanup as gw delete)
gw prune branches # list local branches in main clones that are merged and unused
gw prune branches --gone --fetch --yes # also branches whose upstream was deleted; delete
Pipelines and machine-readable output
List-style commands support --output (-o) with table, json, jsonl, tsv, name, and path formats. table remains the default. Existing --json / -j flags remain supported as compatibility aliases for --output json.
# Select a workspace without parsing a table
gw list -o name | fzf
# Feed workspace paths into another command
gw list -o path | while IFS= read -r path; do
printf '%s\n' "$path"
done
# Process one complete object per line
gw status my-feature -o jsonl |
jq -r 'select(.changed > 0) | .repo'
# Delete a reviewed set of workspaces from newline-delimited stdin
gw list -o name | grep '^old-' | gw delete --stdin --yes
The output formats are available on gw list, gw repos, gw status, and gw ws show. Data is written to stdout; progress and diagnostics are written to stderr. ANSI styling is disabled when output is redirected or NO_COLOR is set.
Interactive menus support type-to-search filtering, arrow-key navigation (single-select), or arrow + tab (multi-select) with an (all) shortcut.
Repos can carry a .grove.toml so every new worktree is ready to work in:
# svc-a/.grove.toml
base_branch = "stage" # branch from origin/stage instead of origin/main
setup = "pnpm install" # run after the worktree is created
To namespace your branches, add a resolve_branch hook to ~/.grove/config.toml. gw create -b feat-login then creates workspace feat-login on branch nick/feat-login. See docs/hooks.md.
[hooks]
resolve_branch = "echo nick/{branch}"
Presets, plugins, hooks, and the full command reference are covered in Workflows and Operations.
Integrations
- grove-herdr — Herdr plugin:
prefix+shift+gprompts for a name, runsgw create, and opens the workspace in Herdr; hooks close it ongw delete. - grove-rex — Rex popup:
cmd+gasks for a name, a preset or repos, and a branch, runsgw create, and opens the workspace as a Rex session; apre_deletehook closes it ongw delete. - Plugins such as gw-dispatch, gw-run, and gw-recipe — see docs/plugins.md.
Upgrading
If you installed with Homebrew:
brew update && brew upgrade grove
If you used the install script, re-run it to get the latest release.
Documentation
- Quickstart — install, first commands, and key concepts
- Workflows — creating, syncing, resetting, and deleting workspaces
- Operations — configuration, hooks, state, and troubleshooting
- Hooks — global hooks and per-repo
.grove.tomlhooks - Plugins — extend
gwwith external commands - AI coding tools — vendor-neutral agent workflows
- Agent skill — teach a coding agent to use
gw
Contributors can start with the Architecture and Integrations notes.
