Blog
How SweepLoom decides what is safe, what it measured, and where the numbers stop meaning what they seem to.
SweepLoom's desktop app was redesigned around nine tabs: Overview, Sessions and History for live pressure; Cleanup, Projects and Explorer for disk; Browser and AI for the workspace; and Settings. What each tab shows, what changed in this release, and the rules every destructive action follows.
A tool that deletes files should be boring on the inside. How SweepLoom's workspace is split into crates, which invariants every crate keeps, why cargo-deny bans tokio, hyper and reqwest, and how the desktop app scans in parallel with nothing but std threads and channels.
Project discovery used to start from the folder the app was launched in. Now it covers every developer folder with fair per-folder budgets, walks on bounded worker threads, and streams rows as they finish. It found 598 projects where the old walk found 237, in less time. How it works, the numbers, and the limits.
Your ~/.claude folder is almost a gigabyte, but almost none of it is sent to the model. How SweepLoom separates always-on context from archive, why history counts as zero, how the estimate is capped, and what a live benchmark says about the limits of this number.
Tools tell an agent what it can do; skills tell it how to behave. SweepLoom's Codex plugin bundles the MCP server with three skills that make review-before-apply the default. What is in it, how to install it today while npm is not published, and where the real enforcement lives.
DerivedData, device support, simulator devices and runtimes, archives and backups all live under ~/Library, and they are not the same kind of thing. How SweepLoom's desktop Cleanup screen tells regenerable cache from native objects and from data you cannot get back.
Ask an agent to free disk space and it improvises with du, guesses and rm -rf. SweepLoom's MCP server gives it eight read-only tools and one gated apply instead. Setup for Claude Code, Cursor, Claude Desktop and Codex, the confirm=true contract, and the limits worth knowing.
SweepLoom is a local-first resource manager for developer machines. What it finds, the three questions it answers, who it is for, and how its CLI, MCP server and desktop app share one engine and one rule: nothing is deleted without plan, revalidate, execute and receipt.
An idle Cursor window holding 7 GB looks like the obvious thing to reclaim. It is also the conversation you were trying to make cheaper. Here is how SweepLoom groups live sessions, why agents stay Keep, and what it offers instead.