Levo help · For your kind of Mac

For web developers: node_modules and package caches

JavaScript projects are small until you install them. A few dozen projects later, node_modules folders and package caches add up to tens of gigabytes. Almost all of it is a download away.

What Levo looks for

node_modules in each project. Reinstalling brings it back from the lockfile.
Package caches: npm, npx, pnpm store, Yarn, Bun, Deno, plus Electron and node-gyp downloads.
Framework build output: Next.js, Nuxt, SvelteKit, Angular, Vite, Astro, Expo and Metro, Turborepo and Parcel caches, and dist folders.
Browser test downloads: Playwright and Puppeteer browsers, and Cypress.
Node versions you installed with nvm, fnm or Volta. Some are listed for you to tick yourself, and the rest only at Aggressive.
Python, Ruby, PHP, Rust and Go projects have the same shape: virtual environments, bundler and vendor folders, target folders and module caches.

Which projects are safe to strip

Levo is careful with a project you’re working in. A node_modules folder is ticked only when nothing is running inside it (no dev server, no open file, no coding agent session) and your agent judges the project idle. A project you used this morning stays unticked.

Your agent adds judgement. A dist folder that’s committed to git is not a build output, and your agent knows the difference.

Dev servers and watchers

A forgotten dev server or watcher is a common reason a fan spins up. Open Free memory, CPU and GPU and your agent lists the ones that have been idle for hours, so you can quit them. See Free memory, CPU and GPU.

A good routine

Analyse, then open Project dependencies.
Pick a cleanup level. Balanced is a good start: it ticks projects your agent judges idle.
Clean up. When you come back to an old project, run npm install (or your tool’s equivalent) as usual.

The package caches only speed up installs, so clear them freely. Without them, the next install is slower and needs the network once.