Request for classic confinement: autoclear

Justification for Classic Confinement

Autoclear, is a system utility that moves and manages user cache directories (~/.cache) and related temporary files across the filesystem. It also provides logging, history of operations, and multilingual desktop path support.

This functionality requires unrestricted filesystem access to inspect, move, and delete directories outside the confined $HOME or $SNAP environment. Under strict confinement, the application cannot reach or manipulate user cache folders and system paths as intended, which makes the tool non-functional.

Because Autoclear is designed to manage user-level cache cleanup and may interact with arbitrary folders depending on user configuration, classic confinement is necessary. The tool does not provide its functionality under strict confinement, since it cannot guarantee correct access to the required directories.

We acknowledge that classic confinement allows broad system access, but this level of access is essential for Autoclear’s purpose as a general system utility.

You did sadly not use the template for your request, so the queue bot that is supposed to add it to the review queue has not picked it up (which means it will go unnoticed)

Please note also that it is a hard requirement that your app fits into one of the supported categories from:

Sadly one of the completely unsupported cases is:

  • access to arbitrary files on the system because the application isn’t designed with confinement in mind

So I think your chances are pretty low (unless you can make out another “supported” category that would override this unsupported case)

1 Like

This request has been added to the queue for review by the @reviewers team.

1 Like

Thank you for the information. I will change the template to the correct one and focus on modifying the function to find a suitable solution.

Thanks @ogra for your response. I’m removing this request from the queue, @Uwabaki feel free to open a new one if needed.

Thanks