Requirements
DevCleaner for Linux 1.1.1 requires Ubuntu 24.04 or newer, on amd64 or arm64. Existing settings and cleaning history stay in place when you upgrade. Download the packages from DevCleaner for Linux.
Install a .deb
The download page has one .deb for amd64 and one for arm64. Save the package, open a terminal in that directory, and install the file you downloaded. For 1.1.1 the commands are:
sudo apt install ./devcleaner-linux_1.1.1_amd64.deb
sudo apt install ./devcleaner-linux_1.1.1_arm64.deb
The download page lists a SHA-256 checksum for each .deb. The same checksums are in /downloads/linux/SHA256SUMS, linked from that page.
Apt repository
The apt repository is https://devcleaner.app/apt/, suite stable, component main, architectures amd64 and arm64. The package does not add this repository. Add the keyring and the deb822 source, then install:
sudo install -d -m 0755 /usr/share/keyrings
curl -fsSL https://devcleaner.app/apt/devcleaner-archive-keyring.gpg | sudo tee /usr/share/keyrings/devcleaner-archive-keyring.gpg >/dev/null
curl -fsSL https://devcleaner.app/apt/devcleaner.sources | sudo tee /etc/apt/sources.list.d/devcleaner.sources >/dev/null
sudo apt update
sudo apt install devcleaner-linux
The package in this repository is the same file as the direct .deb download. A package installed from the repository shows “Updates via apt.” and does not download updates inside the app. Later versions from the repository install with sudo apt upgrade.
AppImage
The AppImage is one file for x86_64 and one file for aarch64. For 1.1.1 those files are DevCleaner-1.1.1-x86_64.AppImage and DevCleaner-1.1.1-aarch64.AppImage, linked from the Linux download page. Ubuntu 24.04 needs the libfuse2t64 package to run an AppImage. If that package is not installed, start the file with --appimage-extract-and-run. The AppImage checks the signed Linux feed and replaces its own file when a newer AppImage is published.
The same bytes are also at /downloads/linux/DevCleaner-x86_64.AppImage and /downloads/linux/DevCleaner-aarch64.AppImage. Both names are listed in /downloads/linux/APPIMAGE-SHA256SUMS. These checksums are separate from the .deb files.
Updates
How an update arrives depends on how you installed DevCleaner.
- Apt. Settings shows “Updates via apt.” The app does not download a package. Install a later version with
sudo apt upgrade. - Direct .deb. On launch, and from Settings → Updates → Check for updates, DevCleaner checks the signed Linux feed. When a newer package is available, the window says that version is available and Update… opens Settings. Review update downloads the signed package, verifies it, and asks you to confirm installation in the system dialog. DevCleaner then restarts.
- AppImage. The same check downloads a newer signed AppImage, verifies it, and replaces this AppImage. DevCleaner then restarts. You can also check from Settings → Updates.
Risk levels in 1.1.1
Linux 1.1.1 uses the same Safe, Warning, and Danger names as macOS. Settings → Risk levels also lists Protected. Quick Clean includes Safe items only.
- SAFE Reconstructible caches. Selected by default when the data is safe to rebuild.
- WARNING May require an app restart or a re-download. Never selected by default. Selecting one asks you to review it before it is ticked, and cleaning asks again before anything is removed. On a new install, Warning cleaning needs an active Pro license or trial.
- DANGER Could remove useful or hard-to-recreate data. Not selected by default, and never part of Quick Clean.
- PROTECTED Shown for information only. Never counted as cleanable space.
Two kinds of row share the Danger name.
Orca (~/orca/workspaces) and Conductor (~/conductor/workspaces) are Danger, unselected by default, and excluded from Quick Clean. An active Pro license or trial can clean them after review. Selecting one asks you to review the selection, and the clean review says a Danger category is selected. A Free install shows that a Pro license is required. These folders are git worktrees: working copies, not a cache. Deleting a workspace removes that working copy, including uncommitted work. The original repository checkout is outside these folders. DevCleaner deletes the workspace folder and does not run git worktree remove, so the parent repository can still list the workspace until you prune it. A custom workspace directory is not scanned. ~/.orca and ~/.conductor are separate from these rows. Cleanup of a workspace is skipped while orca or conductor is running.
The other Danger rows are the High tier. The badge still says Danger, and cleaning stays disabled, including with an active Pro license or trial. The row says “not enabled.” Settings describes them as staying disabled until a dedicated review flow exists. In 1.1.1 those rows are Claude Session Transcripts, Codex Session Memories, Codex Archived Conversations, the Maven local repository, and unused Docker and Podman volumes.
An install that finished onboarding before the Free and Pro cleanup split keeps its earlier manual cleanup of Warning rows and of the Orca and Conductor workspaces. See existing Free installations.
License
One license key activates up to three devices in total. Activating DevCleaner on Linux uses one of those seats. The same key works on a Mac. Settings → Your license shows the limit, and Deactivate this device frees a seat. Safe Quick Clean stays available without a license. Details of the trial and of moving a key are in License, trial & pricing.