Disk usage and safe cleanup (including rootless Docker)
Two screens: Disk only measures, Cleanup only deletes. Cleanup lists fixed, known categories of files that can be re-created, shows the size and the exact command for each, and runs nothing until you confirm.
Disk usage
- Lists the 40 largest folders inside a path (default /), never crossing into another disk; click a folder to open it.
- Shows Docker's own usage: images, containers and volumes with what could be reclaimed.
- Marks a folder that is a Docker daemon's storage (system Docker or a user's rootless Docker) and points you to Cleanup for it instead of deleting files by hand.
- Large disks can take a minute or two to measure; progress is shown.
Cleanup categories
| Category | What is removed |
|---|---|
| Package cache | apt's downloaded package files |
| System journal | journal entries older than 7 days |
| Rotated logs | old, already rotated log files |
| Temporary files | old files in temporary folders |
| Crash dumps | saved crash reports |
| Docker build cache | per Docker daemon, through Docker's own prune |
| Docker unused images | per Docker daemon, images no container uses, through Docker's own prune |
Docker and rootless Docker
Each Docker daemon is handled separately: the system daemon and every user's rootless daemon are listed with their storage folder, running containers and any error. A rootless daemon's category ids end in @u<uid>. Cleanup goes to the daemon it names, through Docker itself. Running containers, the images of stopped containers and all volumes are never touched. If a daemon's sizes cannot be read, cleanup is not recommended for it.
What is never removed
Application data, databases, containers and Docker volumes. Only known files that can be re-created are listed.
Rights
Cleanup needs root or passwordless sudo on the server. Without them sizes may be incomplete and cleanup is not offered.
For AI
server_disk_usage and server_cleanup_scan are read-only. server_cleanup_run runs the cleanup commands of the categories you approve, as root, and needs a human approval for that exact call unless the device or SSH server is on full trust.
- Server overview and live monitoring: See a Linux server's CPU, memory, disks, uptime, pending updates, reboot status and zombie count over SSH, and watch it live on the Dock or the menu bar.
- Docker containers: List Docker containers per daemon (system and rootless), read their logs with secrets masked, and start, stop or restart a container with approval. Nothing is ever removed or pruned by these tools.
- MCP tool reference: Every WECOMMANDER MCP tool, grouped: what it does, its risk and approval rule, where it works (agent devices, SSH servers, Linux only) and its key arguments.