DEEPDRIVECLEANER / THE DDC COMMAND

Fast disk cleanup for developers and agents.

A native app and CLI. For you and your agent. One engine.

Find development leftovers, inspect JSON reports, and preview a cleanup plan before deciding what to remove.

ddc.sh is the CLI guide for DeepDriveCleaner. It is the same product as deepdrivecleaner.app. Explore the Mac app

Get the ddc command

v0.3.0
macOS · Apple Silicon / ARM64 · Standalone CLIdeepdrivecleaner-0.3.0-aarch64-apple-darwin.tar.gz
Download CLI archive

Unpack the archive, put deepdrivecleaner on your PATH, and add ddc as an alias or symlink. For the app and CLI together, use Homebrew:

brew install --cask smartandpoint/tap/deepdrivecleaner

The native app is available for macOS only. CLI build availability is listed separately.

Release availability checked 28 October 2026.

One workflow. In your terminal or through an agent.

These are instructions for the installed tool. This website does not run commands.

01

Inspect

Run a read-only scan. Use JSON when an agent or script needs the full report.

ddc scan --json
02

Preview the plan

See proposed actions without changing files. A scan report is not permission to delete.

ddc clean --dry-run
03

Review and clean

In an interactive terminal, inspect the plan, adjust selections and confirm cleanup.

ddc clean

Interactive cleanup needs a terminal. An agent without a terminal should stop after inspection and preview; do not silently substitute --yes.

Cleaning deletes files. Review the plan and confirm your selection. Disclaimer ↗

Reports your tools can read

JSON reports and published schemas make findings and outcomes inspectable.

Your agents build. You review the cleanup.

Illustrative data · not a scan of your device

Sample total128.4 GiB

Development with agents can leave dependency folders, caches and build outputs. Inspect what is there before choosing what to remove.

Sample sizes, not promised savings. Classification depends on the rule and context.

safe

Download caches

Package download caches refill when you need them. These start selected; where supported, cleanup uses the tool's own command.

~/.npm/_cacache
~/.cache/uv
Homebrew downloads

Selected by default. Review the plan before cleaning.

Checks before cleanup

Understand the boundaries before giving an agent a cleanup task.

Items are checked again

Identity, rule matches, protected paths and other guards are checked before actions. Changed or refused items are skipped with a reason.

Scheduled scans do not clean

Background scans report findings. They do not call the cleanup executor.

Actions are recorded

Review items use the Trash by default where applicable. Other actions can permanently delete files or use a tool’s cleanup command. The journal is not an undo facility.

Explicit selections and non-interactive use

The app uses an explicit item list. Scripts and agents can use this API too, after the intended selection has been authorized.

Preview an existing selection file

ddc clean --items selection.json --dry-run

clean --items consumes the caller’s list without prompting. It does not authenticate human approval. clean --json requires --items. The --yes option also skips interactive questions within its supported scope.

Obtain approval for the specific selection before execution. The CLI reference describes the item format; no executable cleanup list is provided here.

Read the explicit-selection API

These are cleanup safeguards, not a sandbox or a guarantee against prompt injection. They do not prevent a compromised agent from running other commands.

One product. App and CLI. The same engine.

DeepDriveCleaner is the app. ddc is its command. Use a window, a terminal, or your coding agent—both interfaces use the same cleanup checks.

FOR DEVELOPERS + AGENTS

Built agent-first. Open to your contribution.

People and agents develop DeepDriveCleaner with ProjectStore. Read the shared decisions, follow the runbook, and bring a scoped improvement.

Contribution terms ↗ · Source-available · PolyForm Noncommercial