Grove

Use when you want to orchestrate a fleet of independent, parent-level coding agents with Grove — spin up isolated per-task workspaces (tmux + git worktree, host or container) across model providers and harnesses, to divide, parallelize, and independently review large or multi-part work. Covers the CLI verbs and the MCP tool surface by id.

Use when a user wants to set up or change Grove's configuration, for a host/user or for a project. Covers the global user config, the committed project config, machine-local overrides, agents, init scripts, tmux and peek tuning, the TUI theme, and the daemon auth, plus the six-layer cascade, the exact file locations, the full schema with defaults, and a required verification step against the user's installed version.

Use when a user wants to reinstall, update, or upgrade Grove after pulling new code, or when they report seeing the OLD UI / stale behavior after an update ("I still see the old dashboard", "the redesign isn't showing", "I reinstalled but nothing changed"). Covers the editable uv-tool install model, the independently-updated surfaces (package/CLI/TUI, daemon, webapp, plus the opt-in grove-mcp stdio server), the reinstall-vs-restart decision, a required verification pass, and a troubleshooting decision tree for stale processes, stale webapp builds, and browser/proxy caching. Reach for this skill whenever an update "didn't take" even if the user doesn't say the word "reinstall".