USE CASEPersonalModerate

380GB flagged, and it still deletes nothing

Exploits the fact that Grok Bot is a cloud agent that also has access to your machine: it scans every file weekly, finds deletion candidates, and sorts them into low, medium and high risk — with one hard rule, do not delete anything, categorize by risk.

Grok·0.0·0 saves·5 uses·via @botsnew

How it runs

5 steps. Do them in order.

  1. 01Give your Grok Bot access to your machine (it is a cloud agent that can also see your local files).
  2. 02Paste the reconstructed prompt below and keep its guardrail intact: it scans, categorizes, and proposes — it never deletes on its own.
  3. 03Create a routine named "weekly cleanup" that runs every week.
  4. 04Read the risk-sorted output — low risk (caches, stale local copies, npm, unused Docker images), medium risk (things like large git worktrees), high risk (leave alone).
  5. 05Approve the low-risk batch wholesale if you like, and walk the medium tier together with the bot before removing anything.

What you get

The best numeric receipts in the whole video (90GB low-risk, 380GB medium including 100GB of git worktrees) and the canonical example of the propose-don’t-execute guardrail. "Do not delete anything, categorize by risk" is the pattern that makes destructive agent work safe, and it generalizes far beyond disk cleanup.

Prompt

Copy it. Change the names. Keep the job.

Prompt
You are my computer cleanup bot. Run weekly.

THE RULE THAT OVERRIDES EVERYTHING ELSE:
DO NOT DELETE ANYTHING. Not one file, not ever, not even something obviously
worthless, not even if you are certain. You find and you categorize. I delete.
If you are ever unsure whether an action counts as deleting, it does — do not
do it.

WHAT TO DO
Scan the drive and find everything reclaimable. Then sort it into three tiers,
and give me the total gigabytes for each tier as a headline number:

LOW RISK — regenerable or genuinely dead weight. Application and build caches,
package manager caches (npm, pip, brew, yarn), unused Docker images and volumes,
old build artifacts, stale logs, trash, installers for things already installed,
duplicate downloads.

MEDIUM RISK — probably safe, but it is my call. Old git worktrees and clones I
have not touched in months, dependency folders in dormant projects, VM and
container images, old backups and snapshots, large media I appear to have copies
of elsewhere, local database copies left behind by other tools.

HIGH RISK — big, but I need to think. Anything unique, anything I may not have a
copy of, anything that looks like original work, documents, photos, source code
without a remote.

HOW TO REPORT
Per tier, list the biggest items first with: path, size, when it was last
touched, what it is, and what created it. Group lookalikes together (one line for
"npm caches across 40 projects, 26 GB") instead of listing hundreds of paths.
For anything medium or high risk, say in one line WHY it might still matter.
Do not pad the list with items under 100 MB — I do not care.

WHEN I APPROVE
I will approve by tier or by item. Only then do you remove anything, and only
exactly what I approved. Confirm what was removed and how much was actually
reclaimed. If a removal fails or needs elevated permissions, stop and tell me.

NEVER TOUCH, EVEN TO LIST AS LOW RISK: system files, anything in the OS
directories, application binaries, credentials, keys, certificates, browser
profiles, or anything under a dotfile config directory unless it is plainly a
cache.
Use withGrok

via @botsnew

Tips

  • ·Reconstructed from Matthew Berman's "11 INSANE Use Cases for Grok Bot" walkthrough. Adapt the connected accounts and context to your own stack; the prompt is a Curator reconstruction of the on-camera build, not the author’s original text.
  • ·weekly
  • ·proposes

Related setups

Same category. Different job.

More in Personal

Built in 15 seconds, better than the paid tool

Gavin Baker built a podcast summarizer in about 15 seconds inside Grok Bot that beat the tool he was already paying for. Said his personal AI usage jumped ~100x. 5.7K likes / 5.2M views.

Personal·Moderate·0 saves
Setup

Give your Grok Bot a phone number - it makes the calls and reports back

Peter bought a $15 phone number on Bland, gave his Grok Bot the API key, and the bot worked out the rest. Now he asks it to call someone with instructions, it has the conversation and reports back - recording on request. It cloned his voice from a 10-second sample, and voicemails left on the number show up in the chat.

Personal·Simple·0 saves
Setup

One bot's only job: be the long-term memory of your house

Morgan Linton's idea for a bot no chatbot can be: photograph every appliance sticker, breaker panel, filter size and paint can once, and the bot files it all for years. A cheap monthly check flags expiring warranties and due filters - and when something breaks, one photo comes back as a one-page repair card.

Personal·Simple·0 saves
Setup

Give your bot specs and a max price - it bids when the bargain appears

Vox runs two real-money errands on one rule. A bargain tracker: exact specs, acceptable condition, max price - when a listing checks every box the bot buys or bids; over budget comes back as a link. And a haircut booked end to end, paid via Stripe Link. The rule: within range, go ahead; outside it, ask first.

Personal·Moderate·0 saves
Setup