When I upload certain file types such as a PDF or CSV to a Cloud Agent, the agent responds with:
The uploaded file Invoice-XBBU8UZ0-0010 (2).pdf did not reach the VM. The expected path /home/ubuntu/.cursor/projects/workspace/uploads/ does not exist, and a filesystem-wide search for the filename or any recent PDF returns nothing.
I’m having trouble reproducing this. Can you share how you’re attaching the files to the cloud agent? Are you you going through + > Files > xyz.pdf or doing a drag/drop or copy/paste? Does the behavior change depending on which you do?
It doesn’t work either way. Initial report was via drag and drop. Here’s a request ID using ‘+ Files’ (same issue): e536b21d-b45e-42e6-b5b9-c9b0a7ada63e
I noticed this first around a week ago with CSV files and reported it via the Cursor shared Slack for our YC batch.
Expected path /home/ubuntu/.cursor/projects/workspace/uploads/Invoice-XBBU8UZ0-0010__2__b0a4.pdf does not exist; the uploads/ directory was never created.
A filesystem-wide search for *XBBU8UZ0* (retried after 15 s) returns nothing.
Cause: the upload attachment was registered in the message but the file transfer to the VM failed or was skipped.
Next action (under 2 minutes): re-attach the PDF in a new message and I will read it immediately.
Hey @Lewis_Blackwood, thanks for trying both ways, that ruled a lot out.
I think I know what is going on, and it looks specific to your repo. The agent saves attached PDFs and CSVs into its uploads folder using the same file-write step that the agent’s own Write tool uses. If the repo has a Cursor hook that denies the Write tool (for example a rule that blocks edits while on main), that hook also blocks the attachment from being saved, and right now the agent is not told about it, so it goes looking for a file that was never written. Images are handed to the model directly, which is why PNGs still work.
Could you check whether your repo has a .cursor/hooks.json with a preToolUse hook that matches Write? If it does, a quick workaround is to let that hook allow any file_path under /home/ubuntu/.cursor/projects/ (that is where attachments land) and only deny paths inside your repo. After that change, a new Cloud Agent with a PDF attached should be able to read it right away.
Let me know if the hook is there and whether the tweak fixes it for you.