Levo help · Cleaning up

Smartly: what gets ticked and why

Smartly ticks only what looks safe at your cleanup level, so one click on Clean up does the sensible thing.

How an item gets ticked

1. It has to be allowed. The guard checks the item first: not protected, not in use, not unsaved git work. See Locked items.
2. It has to be removable. Your agent or Levo's rules say it can go: regenerable, with a note of how it comes back. User data and "keep" items are never ticked.
3. It has to have sat long enough. Each item has a level at which it becomes tickable, from how it comes back and how long it's been untouched. If that level is at or below yours, it's ticked.

An example

A build cache untouched for two days is ticked at Balanced and Aggressive, not at Careful. An iOS runtime untouched for the same time isn't ticked at any level yet: costly things need Aggressive and a longer wait. A project folder you edited an hour ago is left alone at every level.

Parts

Some rows are a pile of separate parts, like agent sessions. At your level, Smartly ticks the parts it takes and shows the row's size as their sum. If it takes none, the row shows what Aggressive would take, unticked, so a manual tick still means something.

You're always in charge

Ticks are a suggestion. Tick or untick anything before you clean, and read the confirm step, which lists every item. A row's hover says whose call the level was: the agent's or Levo's own rules.

Smartly in notifications and Auto mode

The "Clean up" button on a disk notification cleans the set Smartly ticked when the alert was posted, at your level. Auto mode has its own scope, set in its own pane.