KUDU — TECHNICIAN CLI QUICK REFERENCE
Reviewed 2026-10-10 against the desktop CLI source.
Full reference: https://usekudu.com/docs/agent/cli
Downloads: https://usekudu.com/download

Run the Kudu executable with --cli. If it is not on PATH, use its full
path. In PowerShell use: & "C:\path\to\Kudu.exe" --cli --help

SCAN-ONLY EXAMPLES (do not request deletion)
kudu --cli --help
kudu --cli --version
kudu --cli perf info --json
kudu --cli disk drives --json
kudu --cli scan --system --browser --app --json
kudu --cli history list --json

SAVE A SCAN REPORT
kudu --cli scan --system --browser --app --json > scan.json

JSON stdout contains results; progress goes to stderr. Reports may contain
private paths/device details. Store in the job record; redact before sharing.
Scan totals are estimates, not promises of recovered space.

EXIT CODES
0 Success
1 General error
2 Invalid arguments
3 Permission denied / elevation required
4 Partial success
5 Nothing found
6 Unknown command
7 Threats/issues found requiring attention

BEFORE AUTOMATING CLEANUP
Review the actual machine and obtain approval. Prefer the UI for per-item
selection. Adding --clean to a scan, or using the clean command, requests
deletion; it is not a preview. --all includes the Recycle Bin.
Optional performance cache resets require --include-cache-resets;
optional native maintenance requires --include-maintenance. Leave both
out of routine service scripts. Do not bulk-remove programs, drivers,
services or privacy traces as a default maintenance job.

Portable Windows builds need no installer but can leave local app data.
Cleanup receipts are outcome records, not backups. Verify the original
symptom and disk free space before handing the machine back.