since new upgrade
when we pate code to chat , can not read it and ask for doing again
also when attach file can not read the file
@deanrie @truell20
Hey, do you have an example of this, maybe with a screen recording or screenshots?
Thanks for this, very helpful!
If this is a recent chat, can you send over the request ID for this chat?
You can do this by running the “Report AI Action” command, selecting the chat from the list, and copying the request ID.
This will allow us to see where the AI went wrong here!
thanks for quick reply this is the id 4153fbca-113e-437b-b7fb-831674d57c24
Thanks for that, will investigate with the team soon!
Any updates on this? It’s severely impacting my ability to use Cursor. 50% of the things I paste into chat cannot be seen by the AI.
btw, I noticed that if create a new chat and go back to the previous chat it resets itself somewhat can read pasted text again
Any advice when:
–
Was in middle of YOLOing through my thing and hit 25 YOLO limit - then I get convo too long - but if I move to new Composer, the whole context evaporates? - -I turned on Notepads, and attempted to have it start populating notepads, but it doesnt seem to comply…
Composer is FN amazing, Cursor is what I have needed my whole life… as someone who led people who are utter geniuses, I am very good at explaining what I need to very senior devs, engineers, designers, all disciplins, and have deep knowledge in lots of areas, but have never been an SWE - Devops, but went Director level WAY too early in career, trapped…
But with CURSOR… its like having ALL of those engineers at my beck and call because I am very good at explaing what I want - but cannot build myself. YAY YOLO
(Make the YOLO calls 100)
The conversation too long error should be massively reduced in one of our upcoming versions, as it happens a lot more than it should due to a bug!
We may have some changes coming in the future to notepads, so I’d hold fire and getting them into your workflow in the near future!
I would recommend starting a new chat/composer session, as this doesn’t seem like a bug at the surface, but more of just the LLM misbehaving, which can be hard to fix!
If it keeps happening, make sure you have privacy mode turned off, and send another request ID. I’ll be able to pass that to the team to investigate!
It very clearly started after the most recent upgrade. I’ve been using the llm interface exactly the same way many hours per day for a month and never seen this. I had just upgraded a few days earlier and that was fine… so it was something that changed in a small 2 or 3 day window when I upgraded again.
btw, I haven’t seen it much in the last two days until last night.
Also, I’ve never seen it when I copy/paste from files in the IDE directly. it seems to happen when I copy/paste text from the shell. I know this sounds strange.
It’s possible that something has gone wrong between updates here, so that session isn’t quite as it should be. I’d recommend starting a new, fresh session, and if it still happens, let me know and I’ll raise it with the rest of the team!
It’s the “greater than” character that is the prompt on my shell “>”. If I copy the contents of the shell to a file, delete all “>” it works fine.
So, to be clear, the AI is unable to see pasted code if the code starts with a >
character?
There’s something more going on with copying/pasting from the shell. If I change my prompt character to $ I still get the same issue.
I noticed this too, but only when I have the auto context feature enabled. My guess is that it is related to this.
same, copypasting totally not working anymore.
This thread was 24 days ago, having the same issue. Very frustrating
Hey, if you start a new chat or composer session, does that get things working again?