An interactive shell script to remove unwanted default applications and webapps from Omarchy Linux installations.
Omarchy Cleaner is an interactive shell script that helps users remove unwanted default applications and webapps from Omarchy Linux installations. It solves the problem of software bloat by providing a safe, visual way to declutter the system and tailor it to individual needs.
Omarchy Linux users who want to remove pre-installed software they don't use and maintain a cleaner, more minimal system environment.
Developers choose Omarchy Cleaner because it offers a specialized, user-friendly solution for debloating Omarchy systems with an interactive interface, safe removal processes, and customization options not found in generic package managers.
Quickly and easily remove pre-installed apps and webapps.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a clean, menu-driven selection process for removing apps, making it more accessible than command-line package managers like apt, as shown in the screenshot and described in the README.
Scans specifically for Omarchy's default packages and webapps before removal, reducing the risk of accidentally deleting essential system components, which is highlighted in the 'Safe Removal Process' feature.
Automatically removes keyboard shortcuts linked to uninstalled applications, preventing desktop clutter without manual intervention, as noted in the 'Cleanup of Associated Shortcuts' feature.
Allows users to edit the DEFAULT_APPS and DEFAULT_WEBAPPS arrays in the script to tailor which items are offered for removal, enabling personalized debloating based on the README's customization section.
Only works for Omarchy Linux, so it's useless for users on other distributions or customized Omarchy forks, limiting its general applicability as per the project description.
Relies on running a script directly from curl without built-in verification or offline options, which could pose risks if the source is compromised, a common criticism for such installation methods.
Missing features like dry runs, dependency analysis, or rollback capabilities, which are important for cautious users, as the README does not mention any undo or safety nets beyond the initial scan.