Reclaim the space your dev tools quietly keep.

• 01Build systems

  Derived data, intermediate objects and build outputs that every compile rewrites anyway, usually the largest single thing on a developer machine.

• 02IDEs and editors

  Project indexes, language server data, preview and snapshot caches, and the logs that editors keep long after you have stopped reading them.

• 03Package managers

  Download caches and registries across ecosystems, including versions of packages nothing on your machine still depends on.

• 04Runtimes and SDKs

  Downloaded toolchains, device support files, system images, simulators and emulators, including the ones tied to versions you no longer target.

• 05AI tools and models

  Local model weights, session transcripts and agent caches, which grow quietly and are easy to lose track of.

• 06Containers and VMs

  Virtual disks that only ever grow. Reclaim measures them and hands you the tool’s own prune command rather than reaching inside.

• 07Game engines

  Package caches, derived data and export templates that the engine rebuilds on demand, quietly growing into tens of gigabytes on machines that build games.

• 08Cloud and DevOps

  Downloaded providers, plugin caches, local emulators and logs that infrastructure tools keep around long after the last deploy.

• 09Your projects

  Add your development folders and Reclaim finds the rebuildable artifacts inside each repo, like node_modules and build outputs. Only the artifacts are cleaned, never your code.

What Reclaim will not do.

• 01
  Touch credentials or settings

  Auth tokens, configuration, plugins and content you wrote yourself, like custom commands for AI assistants, are structurally excluded from the catalogue. A unit test enforces it on every build, and the cleanup engine refuses the paths again at runtime.

• 02
  Reach inside another tool’s store

  Where a tool owns its own storage, Reclaim measures it and hands you that tool’s own cleanup command instead of deleting files underneath it.

• 03
  Guess

  Every location in the catalogue is one someone identified, described and rated by hand, and a folder inside a project only counts as an artifact when a marker file proves a tool generates it. Nothing is removed just because it looks like a cache.

• 04
  Phone home

  No accounts, no analytics, no crash reporting, no payment. Beyond an optional update check, nothing leaves your Mac, and you can read the code to confirm it.