node_modules, .venv, venv, env, and conda directories — the heavyweight dependency folders that accumulate across months of development and can consume tens of gigabytes. It calculates exactly how much space you would recover, surfaces orphaned environments without a matching project manifest, and purges everything in a single command.
toolkit clean scan [targetPath]
Recursively walk a directory tree and report every node_modules and Python virtual-environment folder found. For each directory, Toolkit shows its path, type, size, last-modified date, and whether it appears to be an orphan. At the end you get a total recoverable-size summary broken down by type.
The default scan depth is 5 levels. Increase it with --depth if your project tree is deeply nested.
Example terminal output:
toolkit clean purge [targetPath]
Permanently delete the dependency folders discovered during a scan. Purge accepts the same [targetPath] argument and --depth behaviour as scan. Always confirm you know what will be deleted before running a destructive purge.
Orphan Detection
During a scan, Toolkit checks each discovered environment for a corresponding project manifest in its parent directory:- Node.js — looks for
package.json - Python — looks for
pyproject.tomlorrequirements.txt
isOrphan: true). Orphans are safe cleanup candidates — they belong to projects that have been moved, deleted, or archived — and they are highlighted in both the scan output and the JSON report.
--json Output
CleanOperationResult shape returned per directory by toolkit clean purge --json: