grove

grove

CLI tool for managing named workspaces that group git repos and worktrees, with auto-generated Claude Code and VS Code configuration.

• Named workspaces under ~/grove-workspaces/ (configurable via GROVE_ROOT)
• Register git repos, manage git worktrees in a shared pool across workspaces
• Auto-generates CLAUDE.md, .claude/trees.md, and {workspace}.code-workspace VS Code workspace files
• Context inference — most commands detect workspace/repo from CWD

Directory layout

~/grove-workspaces/
  repos/
    my-api -> /path/to/my-api              # global repo symlinks
  worktrees/
    my-api/
      feat-auth/                            # shared git worktree
  myproject/
    workspace.json
    CLAUDE.md                               # auto-generated
    .claude/trees.md                        # auto-generated @-references
    myproject.code-workspace                # auto-generated
    trees/
      my-api/
        main -> ../../../repos/my-api                     # linked (default branch)
        feat-auth -> ../../../worktrees/my-api/feat-auth  # pool

Quick start

Prerequisite: Bun

git clone <repo-url> && cd grove
bun install && bun run build && bun link

grove ws add myproject
grove ws repo add myproject ~/code/my-api
grove ws repo add myproject ~/code/web-client

cd ~/grove-workspaces/myproject   # worktree commands infer workspace from CWD
grove ws worktree add my-api feat-auth --new
grove ws status

Note: worktree add infers the workspace from CWD — run it from inside the workspace directory, or pass --workspace myproject explicitly.

grove ws status outputs a JSON snapshot:

{
  "ok": true,
  "data": {
    "name": "myproject",
    "path": "<GROVE_ROOT>/myproject",
    "repos": [
      {
        "name": "my-api",
        "path": "/path/to/my-api",
        "status": "ok",
        "worktrees": [
          {
            "repo": "my-api",
            "slug": "feat-auth",
            "branch": "feat-auth",
            "type": "worktree"
          }
        ]
      }
    ]
  }
}

Commands

Workspaces — grove ws <command>

Command	Description
add <name>	Create a workspace
list	List workspaces
remove [name] [--force]	Remove a workspace
status [workspace]	Repos + worktrees overview
path [workspace]	Print workspace path
sync [workspace]	Repair symlinks, prune dangling entries

Repos — grove ws repo <command>

Command	Description
add [workspace] <path> [--name N]	Register a git repo
list [workspace]	List registered repos
remove [workspace] <name> [--force]	Unregister a repo

Worktrees — grove ws worktree <command>

Command	Description
add [repo] <branch> [--new] [--from base] [--no-setup]	Create a worktree (shared pool)
list [repo]	List worktrees
remove [repo] <slug> [--force]	Remove a worktree
prune	Clean up dangling symlinks

Exec — grove ws exec <command>

Run standard commands against a repo without needing to know its toolchain:

Command	Description
setup	Install dependencies
format	Format and lint code
test	Run the full test suite
test:file <file>	Run tests for a single file
test:match [file] [--match <pattern>]	Run tests matching a pattern
check	Typecheck the project

setup, format, and test are auto-detected from lockfiles (bun.lock → bun, pnpm-lock.yaml → pnpm, package-lock.json → npm, uv.lock → uv). test:file, test:match, and check require a per-repo .grove/commands.json entry.

Options: --repo <name> (required when no file is given, otherwise inferred from file path), --match <pattern> (filter pattern for test:match), --dry-run (print resolved command without running).

Other