KansoScanning: rules and an agent together
Rules
Measure the usual places in about a minute, the same way every time. What they find can be cleaned as soon as it passes review, while the agent is still working.
Agent
Looks into what rules cannot list: old project dependencies, caches from creative software, data left by uninstalled apps. It works out what each thing is and whether it can come back, and corrects the rules when they are wrong. A folder named Cache that holds original chat images gets marked as not to clean.
Review
A second agent checks every suggestion on its own, and drops whatever it cannot confirm is safe.
Cleaning: two ways
Each suggestion shows its reason and the exact command. Nothing is ticked for you, and nothing is deleted until you confirm.
Clean directly
Kanso runs the suggestions you ticked at once, exactly as they were reviewed.
Let the agent clean
The agent first checks that the path is still as expected and the related app is not running. It runs each step through Kanso, measures again, and reports what was actually freed and what it left alone.
What it can and cannot do
- Agents can only read. A macOS sandbox refuses their writes and deletes in the kernel.
- Only Kanso deletes, after you confirm. It refuses protected places such as your Documents folder and Photos library.
- Kanso has no account and collects nothing. It connects to us only if you let it check for updates.
- The agent runs on your own account. What it reads on your Mac, such as file names and paths, goes to that agent's provider under their terms.
What you need
- Claude Code, Codex or Pi, installed and signed in. A scan takes about 10 minutes and uses your agent's quota. Without an agent, a quick scan still draws the map, but its results cannot be cleaned.
- Full Disk Access, if you want Mail and some apps measured. It is optional.