npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

claude-grove

v0.1.2

Published

Terminal dashboard for running Claude Code sessions in git worktrees

Downloads

821

Readme

grove

A terminal dashboard for running Claude Code sessions side by side, each in its own git worktree.

Install

You'll need Node 22 or later, git, tmux and Claude Code. p (open a PR) also needs the GitHub CLI. grove runs on macOS and Linux.

npm install -g claude-grove

Or from source: clone the repo, then npm install && npm run build && npm link.

Then run it from any git repo:

cd ~/dev/some-repo
grove

| Key | Action | |---|---| | n | New worktree + branch (or check out an existing branch), copy env files, run setup, start Claude and drop you into it | | f | Fan out: start one task in 2–5 worktrees at once (tab changes the count) to compare the results | | c | Compare a fan-out's candidates side by side | | enter | Attach to the session (relaunches with --continue if Claude exited). ctrl-b d returns | | d | Diff screen: changed files (new ones included) beside the selected file's patch, updating live. j/k file, space/b page, J/K line, s only what changed since your last look, esc back | | D | The whole patch against the base in git's pager | | m | Merge the branch into the base in your main checkout | | p | Push and open a PR with gh pr create --fill | | x / X | Remove the worktree / force-remove, discarding uncommitted changes | | v | Create the integration preview, or open a shell in it | | space | Put the selected worktree into the preview or take it out | | V | Remove the preview | | j/k, arrows | Move | | t / w | In compare: run the tests in every candidate / keep the selected candidate and delete the others | | q | Quit (sessions keep running in tmux) | | u | Update the base branch from its remote now. Grove also does this every 2 minutes, fast-forward only: it never merges, rebases or pushes, and leaves the base alone if it has unpushed commits or your edits are in the way | | ? | Help: every key with a one-line explanation |

How it works

  • Worktrees live in ~/.grove/worktrees/<repo>/<branch>.
  • Each Claude session runs in a window of the tmux session grove-<repo>.
  • Claude is launched with --settings ~/.grove/claude-settings.json, which adds hooks that write the session's state (working / needs you / idle) and current activity (the file being edited, the command running, the permission being asked for) to ~/.grove/status/. Your own settings are untouched.
  • Every couple of seconds grove snapshots each worktree as it is on disk (uncommitted and untracked files included, using a throwaway index) and runs git merge-tree on each pair, and on each worktree against the base, to flag merge conflicts before anyone merges. Worktrees, indexes and refs are never touched.

Preview

v creates ~/.grove/worktrees/<repo>/_preview, a checkout of everyone's work merged together, uncommitted and untracked files included, and opens a shell there that first runs setup. Run your dev server in it to try all the branches at once. Every couple of seconds grove merges the base and each worktree in the preview, in name order, and writes the result into it with git read-tree -u --reset. Only changed files are rewritten, so hot reload picks them up. A worktree that would conflict with the ones merged before it is left out and marked ⊘ in the list, so the preview never has conflict markers. HEAD stays on the base, so git diff --cached in the preview shows the combined change.

Every worktree is in the preview by default; space takes it out. Candidates of a fan-out are out by default, and choosing one with space drops its siblings. The preview is read-only: edits made in it are overwritten on the next update (gitignored files like node_modules and build output are left alone). Make changes in a worktree instead.

Config

Optional .grove.json in the repo root:

{
  "base": "main",
  "copy": ["**/.env*", ".claude/settings.local.json"],
  "setup": "pnpm install",
  "claudeArgs": ["--model", "opus"],
  "test": "pnpm test"
}

Defaults: base is origin/HEAD or the current branch, copy copies gitignored .env* files and .claude/settings.local.json, setup is guessed from the lockfile (pnpm/yarn/bun/npm/uv), and test defaults to the package.json test script.

setup, test and claudeArgs let a repo run commands on your machine, and so do the guessed install and test commands (they run the repo's own scripts). The first time grove opens a repo with any of them, it shows them and asks before running them. It asks again if they change. Approvals are kept in ~/.grove/trusted.json. If you say no, grove still works, but without setup, tests or extra claude args.

Fan-out

f asks for a task and starts Claude on it in several fresh worktrees (<task>-a, -b, …), grouped under the task in the list. The compare view shows each candidate's lines and files changed, commits, test result and conflicts, and marks the smallest change whose tests pass with ★. w keeps the candidate you pick and deletes the other worktrees and their branches. Candidates of one fan-out aren't flagged as conflicting with each other, since they're alternatives.

Security

grove runs commands on your machine on a repo's behalf, so it asks before running anything a repo sets. See Config and SECURITY.md.

Development

npm install
npm run build   # or npm run dev
npm link        # puts `grove` on your PATH
npm test

See CONTRIBUTING.md.

License

MIT