My Drive has not been cleaned since 2022

I have been paying interest on the same chore since 2022

August 22, 2026

In partnership with

I opened my Google Drive last week looking for one file and closed it eleven minutes later without finding it. There are folders in there named "new folder 2". There are three versions of a deck I presented once in 2023. Somewhere underneath all of it is the thing I actually wanted. I know the cleanup is a two hour job, and I have known that for four years, which is the entire problem with two hour jobs.

So when someone on r/ChatGPTPromptGenius posted a single prompt that hands the whole chore to ChatGPT through the Google Drive connector, I read it properly instead of skimming it. It picked up thirty seven upvotes quickly, which is not viral, but the comments were coming from people in exactly my position. One of them said it was actually helpful for someone who had not cleaned their Drive in a while. That is the entire market for this thing, and I am standing in the middle of it.

How Jennifer Aniston’s LolaVie brand grew sales 40% with CTV ads

For its first CTV campaign, Jennifer Aniston’s DTC haircare brand LolaVie had a few non-negotiables. The campaign had to be simple. It had to demonstrate measurable impact. And it had to be full-funnel.

LolaVie used Roku Ads Manager to test and optimize creatives — reaching millions of potential customers at all stages of their purchase journeys. Roku Ads Manager helped the brand convey LolaVie’s playful voice while helping drive omnichannel sales across both ecommerce and retail touchpoints.

The campaign included an Action Ad overlay that let viewers shop directly from their TVs by clicking OK on their Roku remote. This guided them to the website to buy LolaVie products.

Discover how Roku Ads Manager helped LolaVie drive big sales and customer growth with self-serve TV ads.

The DTC beauty category is crowded. To break through, Jennifer Aniston’s brand LolaVie, worked with Roku Ads Manager to easily set up, test, and optimize CTV ad creatives. The campaign helped drive a big lift in sales and customer growth, helping LolaVie break through in the crowded beauty category.

*Ad

The prompt does not clean anything for the first several minutes

Here is what separates it from every other "organize my Drive" prompt I have run into. Most of them tell the model to go do the thing. This one refuses to touch a single file until it has built a complete inventory, folder by folder, starting at root.

The author front loads the boring part deliberately. Enumeration first, then verification of that enumeration against a second method, then a report, and only then a request for permission. That sequence sounds like a formality until you picture the alternative, which is a language model making deletion decisions from a partial view of your Drive.

One line in there keeps impressing me. The prompt tells the model not to treat a low limit folder response as exhaustive. That is the author anticipating a specific failure in advance, where the connector returns the first handful of files, the model decides it has seen everything, and hands back a confident and wrong total. Telling a model up front which lie it is most likely to tell itself is most of what good prompting actually is.

Two files named Report.pdf are not one file named twice

The second idea worth stealing is smaller and sharper. The prompt draws a hard line between filename duplicates and confirmed content duplicates, and it reconciles everything through Drive object IDs rather than through names.

Anyone who has ever kept an invoice.pdf in two different client folders understands why that matters. The names match and the documents do not. The prompt reports those two categories separately and never assumes a shared name means a shared file, which reads to me like someone who lost something once and then wrote the fix straight into the instructions.

The retry rule comes from the same instinct. If a connector call fails after previously working, the prompt tells the model to try the same operation again in a fresh attempt before concluding the capability does not exist. Without that, one flaky call produces a confident "this is not possible" and you go back to doing the whole thing by hand.

Then comes the hard gate. Nothing gets deleted, renamed, or moved without a yes from you, and once you say yes, the model keeps a running log of every action it took and everything still waiting on review.

Winning Startups Aren't Bigger. They're Leaner.

Founders deploying AI agents across sales, marketing, and customer service are closing more with smaller teams. 65% more sales leads. Less headcount.

Download the free Practical Guide to Agentic GTM for Startups and start building the stack your competitors dream of.

*Ad

The whole thing, if you want to run it tonight

Use the connected Google Drive tools.

Perform a complete cleanup and organization of my Google Drive.

First, perform a complete hierarchical inventory of My Drive using the validated Drive Enumeration Protocol.

Specifically:
Begin explicitly at Google Drive root.
Use high-ceiling list_folder enumeration (top_k=1000 or greater as necessary).
Do not treat a low-limit folder response as exhaustive.
Preserve Drive object IDs, parent IDs, exact displayed names, MIME/type information, and file/folder classification.
Cross-check every directory using parent-scoped typed searches for folders, images, and documents.
Follow every available typed-search page/continuation token to exhaustion.
Reconcile typed-search results against direct folder listings using stable Drive object IDs.
Preserve miscellaneous file types surfaced by list_folder even when typed search cannot represent them.
Recursively enumerate every folder discovered beneath root.
Restrict the inventory to the My Drive hierarchy. Do not include unrelated "Shared with me" objects.
Preserve exact displayed names.
Number every object.
Clearly identify each object as a file or folder.
Determine empty folders only through direct child enumeration.
If any retrieval boundary prevents a defensible completeness determination, explicitly report the connector limitation instead of guessing.

After the inventory completes:
Report total folders, total files, total items.
Detect and report separately: exact duplicate displayed names, near-duplicate names, empty folders, large files, old exports, obsolete archives, temporary files, other obvious cleanup opportunities.
Do not perform any destructive operation automatically.
Group cleanup recommendations into categories: safe duplicate cleanup, archive cleanup, export cleanup, temporary files, organizational improvements, possible folder restructuring.
Wait for my approval before every delete, rename, move, or other destructive operation.
Once approved, use the Google Drive connector to perform only the approved operations, and keep a running log of deleted files, renamed files, moved files, created folders, and remaining recommendations.
Never assume two files are identical merely because they share the same displayed filename. Report filename duplicates separately from confirmed content duplicates.
If a connector operation unexpectedly fails despite previously validated behavior, retry the same operation in a fresh timeline before concluding the connector lacks the capability.

Once the inventory finishes, you get totals for folders, files, and items, then the cleanup opportunities sorted into buckets: exact duplicate names, near duplicates, empty folders, large files, old exports, obsolete archives, and temp files. That report is the actual product here. The deleting is an afterthought.

PRDs by voice. Bug reports by voice. Ship faster.

Dictate acceptance criteria and reproductions inside Cursor or Warp. Wispr Flow auto-tags file names, preserves syntax, and gives you paste-ready text in seconds. 4x faster than typing.

*Ad

The tradeoff is real, and it is not a technical one

This only works if the Google Drive connector is switched on, which is a genuine decision rather than a checkbox. You are handing a model read and write access to years of your own documents. The original poster was upfront about that, and I am not going to soften it either.

If that sits badly with you, the reasonable middle ground is to move anything sensitive into a separate folder first, or to point the prompt at a single subfolder instead of root, since the scope is one editable line near the top. It is also built specifically for the Drive connector, so it will not run against iCloud, OneDrive, or Dropbox until you swap the tool calls for whatever your platform exposes. The method ports cleanly even when the syntax does not, and the same is true for Gmail, where labels and search filters stand in for folder listings.

The order is the technique

What I am taking from this is not the prompt. It is the sequence, and the sequence transfers to anything you let a model touch on your behalf. Count first. Verify the count against a second method. Report what you found. Ask before you break anything.

Every prompt I have written that went sideways skipped one of those four steps, and it was almost always the second one. A model told to be thorough will simply inform you that it was thorough. A model told to cross check its own enumeration against a different query has to produce two numbers and reconcile them, and that is a much harder thing to fake.

So here is the version that fits into one evening. Run it against a single folder rather than your whole Drive, and read the report all the way through without approving anything. You are not testing whether the cleanup works. You are testing whether the count is right, and if the count is right, everything after it is just clicking yes.