# Suggestion: Allow dragging images as inline file tokens (like files), instead of forcing them as Vision Input **URL:** \ **Category:** Feature Requests\ **Tags:** context, composer\ **Created:** [July 2, 2026, 3:24am UTC](https://forum.cursor.com/t/suggestion-allow-dragging-images-as-inline-file-tokens-like-files-instead-of-forcing-them-as-vision-input/164609 "2026-07-02T03:24:50Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![RainFyh](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@RainFyh](https://forum.cursor.com/u/RainFyh)\ **Post date:** [July 2, 2026, 3:24am UTC](https://forum.cursor.com/t/suggestion-allow-dragging-images-as-inline-file-tokens-like-files-instead-of-forcing-them-as-vision-input/164609/1 "2026-07-02T03:24:51Z")
Hi Cursor Team, I am a heavy user of Composer 2.5 and Agent mode. I love the tool, but I frequently run into a major workflow bottleneck when dragging image assets into the Composer input box. Currently, when I drag an image from macOS Finder into the input box, Cursor automatically forces it to the top as a global **Vision Input**. However, when I drag other file formats (like `.xlsx`), they become inline text tokens/pills that follow the cursor text flow. This behavior causes two critical issues in daily development: #### 1. Hard to describe/reference images in prompts Because images are forced to the top, it is very difficult to refer to a specific image or structure the prompt naturally when mixing text, code, and multiple images. I cannot pin the image to a specific line of my text prompt. #### 2. Critical Issue: Asset Distortion and broken code references When an image is treated as a Vision Input, Cursor seems to compress or process the image data for the model to “see”. If my requirement is simply to tell the AI: _“Help me replace the current background image with this new image asset,”_ the AI fails completely. It no longer sees the image as a raw file asset but as a processed visual context. As a result, it either attempts to output a broken processed image path/base64, or completely messes up the file reference in the generated code. ### Expected Solution I hope there can be a strict distinction between **“Use this image for Vision analysis”** and **“Use this image as a raw File/Asset reference”**. - **Ideal behavior:** When holding a modifier key (e.g., `Option` / `Alt`) while dragging an image, or via a toggle, the image should be inserted as an inline file token (`@image.png`) just like regular files, without being forced into the vision preview at the top. Here is a screenshot of the current mixed behavior for reference: ![image](https://us1.discourse-cdn.com/cursor1/original/3X/b/b/bb62f6ed4e863dc683ab2bc1d9d4287a1c59f4dc.png) Thank you for the amazing tool, hope this UX improvement can be considered! ---
**Author:** ![Tom\_Coustols](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tom_coustols/32/97175_2.png) [@Tom\_Coustols](https://forum.cursor.com/u/Tom_Coustols)\ **Post date:** [July 2, 2026, 3:26am UTC](https://forum.cursor.com/t/suggestion-allow-dragging-images-as-inline-file-tokens-like-files-instead-of-forcing-them-as-vision-input/164609/4 "2026-07-02T03:26:37Z")
upvoted! indeed, it’s hard to refference for specific images if you have multiple, that’s a good feature request! ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [August 7, 2026, 11:49am UTC](https://forum.cursor.com/t/suggestion-allow-dragging-images-as-inline-file-tokens-like-files-instead-of-forcing-them-as-vision-input/164609/8 "2026-08-07T11:49:42Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.