Unable to paste PDFs or images when using Continue working on a previous message

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I click Continue working on a previous message, the chat composer no longer accepts pasted attachments such as PDFs or images using Ctrl + V.
The exact same files can be pasted successfully when using the default/new chat composer at the bottom of the conversation.
Text pasting works as expected, but file attachments are ignored without any error or feedback.
This behavior is fully reproducible.

Steps to Reproduce

Open any chat in Cursor.
Send a message.
Scroll back to that message.
Click Continue working.
Copy a PDF or image to the clipboard.
Click inside the input field.
Press Ctrl + V.

Expected Behavior

The composer opened via Continue working should behave exactly like the default composer and allow users to paste PDFs, images, and other supported attachments.

Screenshots / Screen Recordings

image_for_cursor.png
image_for_cursor.png804×426 7.05 KB

Operating System

Windows 10/11

Version Information

Version: 3.10.20 (user setup)
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

each model

Additional Information

As a software engineer, my suspicion is that the issue is related to the alternate composer instance used by Continue working rather than the clipboard itself.

Possible causes include:

The paste event listener is not attached in the “Continue working” composer.
Clipboard file handling (clipboardData.files / clipboardData.items) is not initialized.
The attachment upload provider or upload state is missing in the alternate composer.
The default composer and the “Continue working” composer use different implementations, with attachment support only enabled in the default one.
A component lifecycle or state initialization issue prevents the upload pipeline from being registered.

Since the same clipboard content works immediately in the default composer, this appears to be a composer-specific state or event registration issue rather than a browser limitation.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey, thanks for the detailed report and the breakdown of possible causes, you’re spot on. This is a real bug: the composer opened via Continue working on a previous message handles file pasting differently than the bottom composer, so PDFs and docs don’t get attached there when you press Ctrl+V. I’ve reported it internally, but I can’t share an ETA for the fix yet.

For now, here are a few workarounds:

  • Use the + or attach button in that composer
  • Drag and drop the file into the input field
  • Paste the attachment in the bottom default composer

If none of these work for you, let me know.