CacheKat 🐈

English | 中文

A TUI to see which dev caches eat your disk — and reclaim space safely, risk-graded. Never touches your data.

Main view (left: cleanable items, select with space, run with c; right: report-only facts, visible but untouchable — the layout itself teaches the safety model) and the confirm gate (nothing cleans without an explicit yes; each row states its plain-words consequence; dry-run d rehearses with the disk untouched):

Main view	Confirm gate

Why

Every developer machine accumulates caches that nobody watches: pip wheels, npm tarballs, playwright browsers (old versions pile up per release), docker build cache, dangling images, stopped containers... A fresh scan answers the only question that matters: who is eating the disk, and what is actually safe to reclaim?

Safety model (the feature)

• Every scan is read-only; cleaning is an explicit, confirmed selection.
• Dry-run mode (d): rehearse exactly what would happen — disk untouched.
• Probes that fail surface as visible error rows, never swallowed.

Install

pipx install cachekat

Or from source: pipx install git+https://github.com/Aeluris/CacheKat.git

Use

cachekat tui             # interactive: scan -> select -> confirm -> clean
cachekat scan            # read-only report: who eats the disk
cachekat scan --json     # machine-readable
# every command accepts --lang auto|en|zh (auto follows the system language)

Docker rows need the docker daemon running — if the TUI shows docker daemon unreachable, start Docker Desktop and press r to rescan.

Roadmap

• Core: probe registry, scan CLI, pip probe, CI (Windows + Linux)
• docker / npm / playwright probes (orphan detection, volumes red-lined)
• Textual TUI: select, confirm, clean, dry-run
• Per-container selection with loud not-a-cache warnings
• i18n: full en/zh, --lang auto|en|zh
• Per-image selection, more cache families (cargo, gradle, ...)

See CHANGELOG.md for details, CONTRIBUTING.md to help, AGENTS.md for the engineering rulebook.

License

MIT — © 2026 Aeluris