Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From grove
Displays current Grove instance slot, sibling instances, port mappings, and rules to avoid cross-instance collisions. Use when working in grove-managed projects, checking ports, or coordinating instances.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grove:contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Grove manages **parallel, isolated instances** of a project. Each instance gets a **slot** (1-9) and unique ports computed as `base + slot * offset`, preventing collisions when multiple copies run simultaneously.
Share bugs, ideas, or general feedback.
Grove manages parallel, isolated instances of a project. Each instance gets a slot (1-9) and unique ports computed as base + slot * offset, preventing collisions when multiple copies run simultaneously.
"${CLAUDE_SKILL_DIR}/scripts/grove-context.sh"
Never use base ports in an instance. If you're in slot 2 and the base port for core is 3068, your port is 3068 + 2*100 = 3268. Using 3068 would collide with the source or another instance.
Port formula: actual_port = base + (slot * offset). Offset is typically 100 for services, 1 for debug/CDP ports.
Check .env files for your ports. After planting, ports are patched into .env files. If you need a port number, read your .env rather than hardcoding.
Other instances are independent. Don't modify files in sibling instance directories. Each instance has its own agent session. Coordinate through the source repo (git), not by reaching into siblings.
grove list or grove list <project>grove list shows green/gray dots per servicegrove doctor prunes instances whose directories are missinggrove uproot <project>/<instance> --force/grove:plant commandnpx claudepluginhub crouton-labs/crouton-kit --plugin groveManages port allocations for git worktrees in local development to avoid service collisions. Books unique ports for postgres, redis, etc., and supports dynamic docker-compose via env vars.
Manages graft for local-first remote dev: runs shimming commands remotely, syncs files bidirectionally with mutagen, forwards ports, sets up connections via flags or graft.yaml, reads status, diagnoses with graft doctor.
Generates bash scripts for dev server lifecycle (start/stop/status/ports) from detected project structure and package manager (pnpm/bun/yarn/npm/Cargo/Go).