◉ANTIGRAVITY LABJP
Articles/Editor View
⟐ Editor View/2026-10-27Beginner

When every dragged file gets swallowed by the agent: workarounds for the terminal, sorted by where they work

Drag an image toward the terminal and a full-window Upload to Agent overlay takes the drop, so nothing arrives. This thread has been open on the forum for months. Here are the reported workarounds, sorted by terminal, file explorer, and a frozen window.

Antigravity IDEDrag and DropUpload to AgentTerminalTroubleshooting12

As an indie developer, I hand store screenshots to an agent by the dozen, so one line in a forum thread stopped me. Drag an image from Finder toward the integrated terminal, and a full-window "Upload to Agent" overlay appears. You let go, and the terminal receives nothing.

The file goes into the agent's context instead of where you meant to drop it. My shoulders tightened just reading it.

The report was filed on February 26, 2026, and people were still adding to it on October 26. What I'd like to say first is this: while you wait for a proper fix, there are workarounds people have reported that keep your work moving. Here they are, sorted by where they apply.

What is happening

According to the reports, since v1.18.3 a full-window "Upload to Agent" overlay captures every drop event once you drag a file over the window. That breaks three things:

  • Dropping an image or file into the integrated terminal to insert its path
  • Moving files or folders around in the sidebar file explorer
  • Rearranging project assets by dragging

The most recent post, from October 26, comes from macOS with Antigravity IDE 2.5.5. The author was running claude in the terminal, dragged an image from Finder, and saw the same overlay with nothing inserted. Holding Shift reportedly helps in an extension's chat panel but not in the terminal.

I have not reproduced this myself on every version, so please treat what follows as a summary of what has been reported.

Where it hurtsReported workaroundCaveat
Getting a path into the terminalSelect the file in Finder, press Cmd+Option+C, then pastePaths with spaces need escaping
Moving files in the explorerOpen Customization from the agent box's three-dot menu, then dragWorks for reporters; may vary by version
Bringing files in from FinderCmd+C / Cmd+V, or right-click a folder and choose UploadMore steps than dragging
The overlay is stuckRun "Developer: Reload Window" from the Command PaletteSave unsaved edits first

1. For the terminal, copy the path and paste it

The most dependable option looked like giving up on dragging. Select the file in Finder and press Cmd+Option+C, and its path goes to the clipboard. Paste it into the terminal.

There is one trap. If the copied path contains a space, the pasted command can break halfway. The asset folders behind my wallpaper apps often have spaces and Japanese characters in their names, so that was worth handling up front.

I wrote a small function that puts a shell-escaped path on the clipboard.

# Add to ~/.zshrc or ~/.bashrc
# Copies an absolute, shell-escaped path of the given file to the clipboard.
# macOS only (uses pbcopy)
pp() {
  local dir base
  dir="$(cd "$(dirname "$1")" && pwd)" || return 1
  base="$(basename "$1")"
  printf '%q' "${dir}/${base}" | pbcopy
  echo "copied: ${dir}/${base}"
}

Running pp "shot 01.png" leaves something like /Users/…/shot\ 01.png on the clipboard. I build the absolute path with cd and pwd because older macOS versions have no realpath. I tested the escaping against a file name containing a space.

Why bother? A missing escape makes the agent run a command against a file that does not exist. Glancing at the end of the pasted path before you press Enter is a cheap habit to pair with it.

2. In the explorer, try the agent box setting

Several forum posts say that choosing Customization from the agent box's three-dot menu made dragging into the explorer work again, and one person noted it kept working after closing the agent view.

This is not an officially documented procedure. It is what happened on other people's machines. I don't use an undocumented workaround when I'm moving files I can't afford to lose. If you try it, do it first with throwaway files.

3. If the window is stuck, reload it

If the overlay stays and the window stops responding, open the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on macOS) and run "Developer: Reload Window". Only the window reloads; your project is untouched. Unsaved edits can be lost, so save first.

What I would not do

Some replies suggest rolling back to a version before v1.18.3. The person who suggested it also said it isn't sustainable, and freezing updates means missing every other fix too.

I'd rather let go of dragging and move to handing over paths. It costs a little convenience, and in return each step of the job becomes something I can read back.

Your next step

Try one disposable file in the version you use now. If the drop doesn't land, start from the first row of the table and use path copying. I plan to peek at the thread now and then to see whether a fix has been announced.

If other editor behavior also seems to have changed since the update, The IDE vanished after Antigravity 2.0: four checks before you try to restore anything may help. And if you suspect something else is wrong with the terminal itself, the diagnostic guide for a terminal that won't start or run commands covers the next round of checks.

Share

Thank You for Reading

Antigravity Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

⟐ Editor View2026-10-05
The IDE vanished after Antigravity 2.0: four checks before you try to restore anything
After updating to Antigravity 2.0, the familiar editor, settings, and extensions were gone. Here is why the config folders split in two, how to restore them without overwriting anything, and what to watch for when running the IDE next to 2.0.
⟐ Editor View2026-09-21
The Night Red Squiggles Filled My MCP Config, and What I Checked Before Editing
Red squiggles across your MCP config don't mean the servers are down. Schema validation in the editor answers a different question than the runtime does. Here's the order I now follow, starting with the status rings in /mcp.
⟐ Editor View2026-08-23
A Triage Order for WebP and Opus Attachments That Never Reach the Agent
Hub 2.9.1 added WebP attachments on August 20, and CLI 1.1.17 fixed Ogg-family audio being rejected by the model on the same day. Here is why rejection happens on the sending side rather than in the file, with the MIME results I actually measured.