Command-Line Interface (CLI) Reference

Run the desktop executable with --cli. Without that flag, the desktop app is not being invoked in CLI mode. Use the executable’s full path if kudu is not on PATH, and consult the installed version’s help before scripting.

kudu --cli --help
kudu --cli --version
kudu --cli <command> [subcommand] [options]

For a Windows portable build, extract the ZIP or use the portable EXE from the download page. In PowerShell, a quoted executable path needs the call operator:

& "C:\path\to\Kudu.exe" --cli --help

Portable does not mean no local data: settings, history, and logs can remain on the machine. Apply your service-record retention policy.

Start with Scan-Only CommandsCopy Anchor Link

These commands do not request cleanup or configuration changes:

kudu --cli perf info --json
kudu --cli disk drives --json
kudu --cli scan --system --browser --app --json
kudu --cli history list --json

On Windows, drive analysis uses the drive name without a colon:

kudu --cli disk analyze C --json

Save a scan report with output redirection:

kudu --cli scan --system --browser --app --json > scan.json

With --json, result output goes to stdout and progress goes to stderr. Reports can contain paths and device details. Keep them in the appropriate job record and redact before sharing publicly.

File CleanupCopy Anchor Link

Prefer the UI when you need per-item selection. Do not assume a previous scan command’s selections carry over to a later cleanup invocation. --all is a broad selection and includes Recycle Bin cleanup when used for cleaning.

Performance-cache resets are excluded from ordinary CLI cleanup unless --include-cache-resets is supplied. Optional native maintenance needs --include-maintenance. Leave both out of routine scripts unless the specific action has been reviewed and approved. See Cleaning Tools for their consequences.

Other Inspection CommandsCopy Anchor Link

Availability varies by platform and installed services. Scans are not approval to apply every reported change.

The current desktop CLI does not expose repair scan, repair fix, or services optimize. Do not use older examples that promise blanket SFC/DISM/CHKDSK repair through those commands.

Commands That Change the MachineCopy Anchor Link

Review the installed help and obtain approval before using action commands. Examples of supported syntax include:

• startup disable NAME / startup enable NAME
• services disable NAME / services enable NAME / services manual NAME / services auto NAME
• updates run ID1,ID2 (or --all for an explicitly approved bulk update)
• drivers clean NAME1,NAME2 and drivers update ID1,ID2
• debloat remove PACKAGE1,PACKAGE2
• leftovers clean --path PATH (repeat --path for each explicitly reviewed leftover)
• restore-point create DESCRIPTION (Windows)
• repair gpu-restart (Windows, administrator; a display-adapter restart, not a generic repair)

Each requires the kudu --cli prefix. Keep driver removal, services, privacy changes, and program removal separate from routine cache maintenance. Bare leftovers cleanup and --all are not substitutes for explicit reviewed leftover paths.

Exit CodesCopy Anchor Link

A scan that finds nothing can return 5. Do not classify every nonzero result as a crash. Inspect both the exit code and result payload, including partial failures.

Scheduling and Headless UseCopy Anchor Link

For attended desktop maintenance, start with Kudu’s Scheduler, which supports conditions and task selection. Test commands on the intended machine before scheduling them through Task Scheduler or cron. An unattended clean --all job is not the default recommended technician workflow.

Linux service installation and --daemon are separate from a scan-only visit. See the Linux agent installation guide and Cloud setup before enabling persistent monitoring.

The repair-shop & IT toolkit includes a downloadable scan-only quick reference. This page was checked against the desktop CLI source on October 10, 2026; the installed executable’s help is authoritative for its version.