Apps

Claude Code Cache

Claude Code stores reusable download and plugin cache data under its .claude cache folders so it does not have to fetch the same packages, plugin artifacts, and temporary extracted files every time a tool or extension is needed. Those caches can accumulate outdated archives, partially downloaded files, and stale plugin metadata after updates or interrupted installs, leading to repeated download failures or plugins that refuse to load correctly. Kudu removes the disposable contents of ~/.claude/cache and ~/.claude/plugins/cache while preserving projects, checkpoints, conversation history, configuration, plugins, backups, and shell snapshots.

Why it matters

Why clean Claude Code Cache?

  • A partial or interrupted package download leaves truncated archives in the cache, so Claude Code keeps reusing bad files and you see repeated install or update failures for the same component
  • Stale plugin cache entries from an older plugin build can make a plugin fail to initialize, which shows up as missing commands, startup errors, or a tool that never becomes available
  • Cached extracted plugin artifacts can drift from the currently installed plugin version, causing version mismatch errors and odd behavior immediately after an update
  • Corrupted metadata in ~/.claude/plugins/cache can send Claude Code into repeated retry loops, where plugin setup runs again and again but never completes successfully
  • Old download archives pile up in ~/.claude/cache over time, consuming noticeable disk space even though the app no longer needs those superseded package files
  • A broken cached dependency bundle can slow first use of a plugin because Claude Code repeatedly validates, rejects, and refetches the same artifact before finally rebuilding a clean cache
What gets cleaned

Cache paths Kudu targets

Windows

~/.claude/cache
~/.claude/plugins/cache
Frequently asked

Common questions about Claude Code Cache

Free & open source

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.