Using Gemini 3.8 Flash (High) in Antigravity to Organize Downloads

On November 8, I asked Antigravity to reorganize and rename files in my Downloads folder, including images with unclear names. The session metadata identified the model as Gemini 3.8 Flash (High).

The task was to inspect the files, give them more useful names, and suggest folders based on their contents. I also asked for similar help with screenshots on my Desktop and PDFs in Documents.

This is a job for a tool-enabled agent with access to the folders you authorize. The model does not gain access to your computer just because you ask it to organize Downloads in a normal chat.

The run also showed why folder cleanup needs checks. Moving a file can break something that expects to find it at its old location. A useful workflow includes a preview, a record of changes, and verification afterward.

What I actually asked

My original request was:

“I need you to reorginize and rename files in my downloads folder again, I have tons of img without names that also might need to be put in folders around what they are and things that need cleaned up do the rename and make suggestions around cleanup in that folder”

I also used these prompts for related tasks:

“Can you rename the screenshots in my desktop, downloads that have the default names to be able to tell what they are?”

“Can you do this same thing with the pdfs in Documents”

Those requests describe a useful goal. A screenshot filename might tell you when it was captured without saying what it shows. A downloaded PDF might have a generated filename that means little to the person who saved it.

An agent that can inspect the contents can propose names that are easier to recognize and search for. It still needs to leave uncertain files alone rather than turn a guess into a confident filename.

What the verification found

The run’s manifest recorded 338 move entries. A follow-up check accounted for all 338: 313 items were at their recorded destinations, and 25 were in Trash.

The 25 items in Trash were seven installer packages and 18 already-broken symbolic links. There were no ordinary documents or media files among those 25 items.

That accounts for the recorded items’ locations. It does not, by itself, validate every new filename, folder choice, or dependent workflow.

Moving assets also disrupted part of my blog intake workflow, which was subsequently repaired. A folder can look tidier while a process elsewhere stops working.

Before trying this on your own computer, make a current backup and consider testing on a copy of a small folder. Inspect the proposed changes and the results. Keep any move to Trash or deletion as a separate decision that requires your explicit permission.

Start with an inspection

The prompts below are suggested templates for a more controlled workflow. They are not quotations from my original session. All example filenames are invented.

Start with one folder and ask the agent to inspect it without making changes.

Example prompt

“Inspect my Downloads folder without changing anything. First tell me which tools and folder access you have. Summarize the file types, existing folders, and files with unhelpful names.

Propose a simple organization plan. Flag symbolic links, shortcuts, application bundles, project folders, and anything that might be referenced by another app or workflow. Leave those items unchanged.

Do not rename, move, delete, send to Trash, overwrite, or modify any files yet. If you cannot inspect a file’s contents, say so rather than guessing.”

A symbolic link points to another location. Moving the link, following it into another folder, or changing its target can have consequences beyond the folder being cleaned. A broken link should be flagged for review, not automatically removed.

An agent may be unable to discover every application dependency. Tell it about folders used by scripts, publishing tools, photo libraries, or other workflows you know about.

If the files contain private information, check how your chosen tools process their contents before granting access. Access to a folder is not a reason to upload its contents to additional services.

Rename screenshots by what they show

For screenshots, useful names usually describe the screen or subject and one distinguishing detail.

For example, an illustrative rename might be:

Screenshot 2026-11-08 at 10.24.30.png
→ wireless-earbuds-pairing-settings.png

The proposed name should come from visible content, not an assumption about why the screenshot was taken.

Example prompt

“Using the inspection-only rules above, review up to 20 screenshots with default or unclear names in Downloads.

For each one, show the current filename, a proposed descriptive filename, and a short explanation based on visible content. Use lowercase words separated by hyphens and preserve the original extension.

Keep names concise. Do not infer people’s identities, add sensitive personal details, or invent dates or context. Flag uncertain or unreadable images for my review.

Show the proposals only. Do not rename or move anything yet.”

Starting with 20 files makes the naming approach easier to review. If the names are too vague or too long, you can correct the approach before applying it more widely.

Renaming and moving can also be separate steps. A file may only need a better name.

Give PDFs useful names without guessing

PDFs need slightly different rules. A title, document type, or clearly printed date may help. The download date does not necessarily tell you when the document was written.

A scanned PDF may require optical character recognition, or OCR, which can misread text. An encrypted or unreadable document should be left for review.

Example prompt

“Inspect up to 20 PDFs with unclear names in my Documents folder. Do not change them.

Propose filenames based on the document’s visible title, subject, and document type. Include a date only when the document clearly establishes what that date means. Preserve the .pdf extension.

Do not include account numbers, addresses, medical details, or other sensitive information in filenames. Flag scanned, encrypted, unreadable, or ambiguous documents instead of guessing.

Show the current name, proposed name, and supporting evidence for each proposal.”

An illustrative name such as conference-program.pdf may be sufficient. A filename does not need to summarize every detail in the document.

Use folders you will recognize later

The folder structure should help you retrieve files, not simply reduce the number of items visible in Downloads.

Broad folders such as Screenshots, Reference Images, and Documents can be a starting point. A topic folder may be more useful when it brings related images and documents together.

Avoid creating dozens of folders based on distinctions you are unlikely to remember.

Example prompt

“Using the files you have already inspected, propose a small number of folders that would make them easier to find.

Show which files would go into each folder and explain any uncertain choices. Preserve existing project folders. Do not move symbolic links, shortcuts, or files with known workflow dependencies.

Keep ambiguous items in their current locations and list them for review. Show the plan without making changes.”

You can approve the folder plan separately from the proposed filenames.

Apply one approved batch and record the results

Once the preview looks sensible, explicitly identify the batch you want applied.

Example prompt

“Apply only the rename and move proposals I have approved for this batch.

Before changing anything, check for filename collisions and save a manifest in the review location we agreed on, outside the folder being reorganized. Record each original path, proposed destination, and operation.

Do not overwrite existing files, delete anything, send anything to Trash, follow symbolic links, or change file contents. Stop on unexpected conditions rather than improvising.

Update the manifest with each operation’s actual result, including failures and skipped items. Then verify the batch before proposing any further changes.”

For ordinary files, recording a content hash before and after the operation can help confirm that the contents stayed the same. The agent should say what it actually checked rather than simply reporting that everything worked.

Keep the manifest somewhere you can find without relying on the newly organized folder. It helps explain what changed, but it cannot replace a backup of the files themselves.

Keep cleanup suggestions separate from deletion

“Clean up Downloads” can mean several things: rename files, group them, archive them, or delete them.

My original request asked for cleanup suggestions. Moving items to Trash or deleting them should be a separate, explicit decision.

Example prompt

“Suggest possible cleanup actions, but do not delete, send to Trash, archive, or move anything.

List suspected duplicates, old installers, broken links, and other candidates with the reason for each suggestion. Do not assume an old or large file is unnecessary.

For suspected duplicates, distinguish exact content matches from files that merely have similar names or appearances. Where possible, compare content hashes. I will decide what to keep.”

Even exact duplicates can serve different purposes when an app or project expects a copy at a particular location.

Verify the files and the workflows

The final check should cover the files and the things that use them.

Open a sample of renamed images and PDFs. Check important shortcuts and workflows. If a publishing process watches a folder, test that process too.

Example prompt

“Verify the approved batch against the manifest.

Report confirmed operations, failures, skipped items, and unresolved discrepancies separately. Check that expected destinations exist and, where recorded, that file hashes match.

If an item is not where the manifest says it should be, investigate and report its verified location or clearly mark it unresolved. Do not make further changes to resolve a discrepancy without showing me the proposed action.

Prepare a rollback plan for this batch, but do not execute it or overwrite anything.”

A rollback plan also needs checking. If files have changed or moved again since the cleanup, reversing every logged operation blindly can create another problem.

My takeaway

Organizing files with a tool-enabled AI agent is a practical use case to test on a small, backed-up folder. The useful part is connecting a file’s contents to a name you can recognize later.

The November 8 run also shows why an operation count is not enough to judge the result. All 338 recorded items were accounted for, but moving assets still disrupted a workflow that needed repair.

Start with an inspection, review the proposed names, and approve a small batch. Keep deletion separate. Then check the results before expanding the job to the rest of your computer.