Repository navigation
Releases
0.3.0
This release cleans more of what you'd expect, and refuses more of what you wouldn't want to lose.
- The RubyGems rule works again for projects that bundle gems from Git. It keeps Bundler's Git clones and deletes the rest of the gem cache, through a new
keep_namesoption for rules (#25). - DerivedData beside an Xcode project or workspace can now be cleaned when its package clones match the project's
Package.resolved(#28). - Plonge recognizes Git directories that share objects with another repository, such as a linked worktree's, and refuses to delete a cache that holds one (#27).
- If Paseo reports an agent that Plonge can't read, Plonge treats every project as busy (#24).
cleannow lists the roots it skipped, and a rule that reads an empty labeled path is skipped the same way whatever the order of the output (#26).
0.2.1
The built-in Xcode cleanup is now as careful as the rest of Plonge.
- Plonge now refuses to delete a stale DerivedData folder that holds a Git repository with work Git can't restore, such as a local commit or an edited package checkout. Folders that hold only Xcode's own package clones are still cleaned, and the report counts only what it deletes (#21).
- The agent skill now says what happens when Plonge can't read Paseo's status (#23).
If you build Plonge from source, mise run check replaces make check (#22).
0.2.0
Plonge now has rules for every core tool that mise installs, and it's more careful about what it deletes.
New rules:
- .NET:
binandobjbeside a project file, and the NuGet caches (#7) - Zig:
.zig-cacheand Zig's global cache (#8) - Python:
.tox,.nox, andbuildanddistbeside a Python project (#9) - Bun, Deno, and Yarn 2 and later: their global caches (#10)
- Swift Package Manager: the shared cache (#12), and
.buildfolders whose dependency clones SwiftPM can restore (#19) - Elixir and Erlang: Mix
_build, and the Hex and Rebar3 package caches (#13) - Rust: Cargo's registry (#14)
- Ruby:
vendor/bundle, Railstmp/cache, and the RubyGems cache (#15) - Java: Gradle
buildoutput and caches, and the Maven repository (#16)
Plonge now refuses to delete a cache that holds a Git repository, in a project (#11) or a global cache (#17). It also refuses caches that hold data a rebuild can't restore, such as a Mix release or a Maven artifact from mvn install.
Fixes:
- Plonge didn't recognize projects where a Paseo agent was running, because it didn't expand
~in Paseo's paths. It does now, and if it can't read Paseo's status, it treats every project as busy (#3). --rootwith a folder of repositories no longer hides the mise projects inside it (#5).mise-toolsmeasures mise's own installs directory, including a customMISE_DATA_DIR(#6).- Freed-space estimates are closer to the truth: a dry run labels a prune rule's size as the whole cache,
--applyreports the change in free space, and on macOS, sizes account for APFS clones (#20).
Rules can now delete a folder's contents, read a path from a tool's output or an environment variable, and protect paths inside a cache. See the rule reference.
0.1.1
Plonge now has prebuilt binaries for macOS and Linux, on amd64 and arm64, so you don't need Go to install it.
With Homebrew:
brew install mattt/tap/plonge
With mise:
mise use -g github:mattt/plonge
Or download the archive for your platform below.
This release also adds plonge --version.
0.1.0
Plonge finds the caches that developer tools and coding agents leave on disk, and it deletes the ones its rules cover. It gets your projects from mise, and its rules are TOML that you can extend.
plonge scan and plonge clean delete nothing. plonge clean --apply deletes cache folders that Git ignores and that hold no tracked files, in projects with no activity for 24 hours.
plonge clean --global --apply runs cleanup for mise, uv, pnpm, and stale Xcode DerivedData. Rules that clear a whole cache, for Go, npm, Yarn, pip, and Homebrew, also need --include-clear.
Coding agents can use Plonge through plonge mcp or the skill in skills/plonge, and plonge disk --warn-below 20GiB works in a session hook.
Install it with Go 1.26 or later:
go install github.com/mattt/plonge/cmd/plonge@latest
Or with mise:
mise use -g go:github.com/mattt/plonge/cmd/plonge@latest
This first release doesn't cover everything that mise can install. What Plonge covers lists each tool and its gaps; dotnet, elixir, erlang, ruby, and zig have no cache rules yet.