lorecampa/groove
lorecampa/groove has 9 GitHub stars and 0 forks. GitHot measured +2 stars in 24 hours. Last checked 2026-11-16 19:40 UTC. Last push 2026-11-14.
Measured star growth
- in 24h
- +2
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- 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
🌳 Reusable Git worktree pools and local checkpoints for coding agents and CI. Built in Rust.
Developer ToolsREADME.md
Original
Groove
Reusable Git worktrees for parallel coding tasks.
Groove gives each task its own checkout from a bounded pool. Reserve a workspace, run commands, and save the result before returning it. Reservations survive shell exits and crashes until you explicitly release them. No daemon is required.
For example, a coordinator handling 20 independent fixes can use a pool of four workspaces. It assigns tasks to available slots, waits or retries when the pool is full, and saves each result before returning the slot for another task.
Your agent runner handles task scheduling, agent communication and result integration. Groove handles workspace allocation, reuse and recovery. Capacity bounds reserved workspaces; the runner controls agent concurrency and resource use.
Install
Requires Linux or macOS 13+, Git 2.40+ and local storage (APFS on macOS). Building from source requires Rust 1.89+.
cargo install --locked groove-cli
The package is groove-cli; the installed command is groove.
Cargo builds the latest published release locally.
Use Groove with your coding agent
Open your project in your coding agent and paste:
Set up Groove in this project using:
https://github.com/lorecampa/groove/blob/main/docs/install.md
Install anything missing and configure this agent to use Groove
for coding tasks in this project by default. Keep this preference
personal to me. Reuse existing pool settings; if a pool needs to be
created, ask me how many workspaces it should have.
Tell me if I need to restart the agent.
After setup, give your agent tasks normally. You don't need to mention Groove in every request.
Manual setup and supported agents.
Use a workspace
From a Git repository with at least one commit:
groove init --capacity 4
groove acquire --task fix-parser
# Work and run tests directly in the printed checkout path.
groove release --save --task fix-parser
New pools put checkouts in ~/.worktrees/<project>-<repo-id>/<pool> on Linux and
macOS. Set a different parent with
groove config global set worktrees.root=/absolute/worktrees, or choose an exact
pool location with init --worktree-root. Existing pools keep their locations.
Acquisition returns a checkout path with detached HEAD. Work in that path, stop
all writers, then run groove release --save to pin a local snapshot and free the
slot. Recover its files and staging state with:
groove snapshot restore SNAPSHOT_ID --to ../recovered-parser
Ignored files are excluded from snapshots. release frees a slot without saving
a snapshot; background preparation or the next acquisition can discard its
contents. Nothing is merged or pushed automatically.
Pools can separate workflow capacity, cleanup and caches. Use groove pools to
list them and pass the same --pool NAME on each pool command. Omitting it selects
default. Pools share Git branches, objects and configuration; they are not
security sandboxes. See operations for repository compatibility
and ownership boundaries.
Command reference
CLI help is the reference for commands, options, defaults and command-specific recovery instructions:
groove --help
groove acquire --help
groove destroy --help
For scripts, add --json to each command. Every response, including
errors and help, is one versioned JSON object. Check ok and the exit status
before using result.worktree_path. Use a request key to retry acquisition and
retain the lease ID for subsequent retries; see the portable skill.
Guides
- Agent skill: workspace selection, retries and handoff.
- Operations: pools, deletion, shared state and supported repositories.
- Snapshots: capture, recovery and retention.
groove COMMAND --help: inputs, JSON output contracts and recovery for integrations.- Contributing: development and validation.
- Security: supported versions and private vulnerability reporting.
Licensed under MIT or Apache-2.0, at your option.
