lopper

Clean up the Git worktrees you and your agents left behind.

Worktrees end up all over the disk. You create some by hand, coding
agents create one per task, and every tool keeps them in a different
place. Each one is a copy of the project with its own node_modules,
.venv or Rust target/, and can take up gigabytes.

Git lists worktrees one repository at a time. Nothing shows you all of
them, which repository each one belongs to, or how much space it takes.

lopper finds them and puts them in one list, so you can see what is
there and remove what you no longer need.

Install

macOS and Linux:

curl -fsSL https://lopper.dev/install.sh | sh

Windows, in PowerShell:

irm https://lopper.dev/install.ps1 | iex

With Go:

go install github.com/shinokamix/lopper/apps/lopper/cmd/lopper@latest

Binaries are also on the releases page.
Each release attests that its archives and installers were built by this
repository's release workflow. To check a file you downloaded:

gh attestation verify lopper_darwin_arm64.tar.gz -R shinokamix/lopper

Usage

lopper              # interactive UI, scans home and temporary directories
lopper ~/code       # scan a specific directory
lopper scan --json  # JSON output
lopper rm ../wt     # remove if safe, --force otherwise
lopper update       # update to the latest release

lopper checks GitHub for updates in the background.
Set LOPPER_NO_UPDATE_CHECK=1 to disable the check.

lopper remembers where it found repositories, in lopper/repos.json
under your user cache directory, so that the next scan lists their
worktrees first and finds the rest while you work. The cache only
changes how soon worktrees appear, never which, and nothing is removed
without being checked again. Set LOPPER_NO_CACHE=1 to scan without it.

Contributing

See CONTRIBUTING.md. Security issues go through
SECURITY.md.

License

MIT