DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to clear developer caches without permanent deletion with Janus

Measure build and package caches, see what each costs to lose, and move the ones you pick to the Trash.

Who it is forA developer whose disk is filling up with package manager, build, browser, and editor caches.

The problemDeveloper caches grow silently, and deleting them by hand risks removing things that are expensive to rebuild or still in use.

The outcomeYou see the size and cost of losing each cache, and the ones you clear go to the Trash so the choice can be reversed.

What you need first

  • A Mac running macOS (the README says macOS only)
  • Claude Code or Codex installed and signed in to at least one account
  • Homebrew, or a manual download of the latest .dmg from Releases
  • Xcode Command Line Tools if you build from source

Steps

  1. Install Janus with brew install --cask --no-quarantine ramitvishwakarma/tap/janus, or download the .dmg from Releases and open it.
  2. Open the Storage tab and wait for the fixed list of cache directories to be measured.
  3. Quit any app whose cache is greyed out and shows a Quit it link before clearing it.
  4. Select the caches you want to remove and clear them, which moves them to the Trash.
  5. If you want Downloads or Trash covered, grant Full Disk Access in System Settings, then Privacy & Security.

Prompt for your agent

Using the Janus repo at RamitVishwakarma/Janus, list the developer cache directories Janus measures on this Mac and their sizes. Report which ones are greyed out because their app is running. Verify that nothing was deleted permanently by checking that cleared items appear in the Trash.

Caveat. Downloads and Trash are behind macOS privacy controls, so they are only covered after you grant Full Disk Access.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page