Cursor v1.3 - Pre-release Discussions

Announcements Release Discussions
27

That’s to be expected. They are bringing visibility into the large token usage costs we incur.

Every tool call loads the entire chat context. That’s how the Responses apis of most LLMs work.

So first chat message sent to agentic is [a1]
second tool call sends [a1] + [a2] to the LLM
third tool call sends [a1] + [a2] + [a3]
fourth tool call sends [a1] + [a2] + [a3] + [a4]
fifth tool call sends [a1] + [a2] + [a3] + [a4] + [a5]

tokens = 5*[a1] + 4*[a2] + 3*[a3] + 2*[a4] + [a5]. with recurring ones being from the cache at 10% read cost, but still.

then second chat message sent to agent is [b1]
second tool call sends [b1] + [b2] to the LLM
third tool call sends [b1] + [b2] + [b3]
…etc

To keep Agentic token usage as low as possible, you really need to limit each chat to 1 or 2 messages sent (press the ENTER key only once or twice)

Please correct me if I am wrong

28

What the hell is going on here?

  1. I never signed up for the beta version, and for some reason, I am on it
  2. After only a few requests, I am being advised to start a brand new chat
  3. And how come when I go to a previous chat higher in the conversation, I am not given the option to revert the code?
  4. All in all, why? What is going on over there at Cursor.ai (I only signed up this month, and this is certainly not a good look)
1 Like
29

Hey! Sorry to hear this. 1.3.0 is not in beta - it is being rolled out over the next week. We believe we fixed the summarized/new chat issue - are you still seeing it? Could you send me a request ID at [email protected]? I apologize for this, we’re on it and hope we have it resolved shortly.

30

Literally just signed up for Ultra, was going very well the last month, and now after upgrading, I’m having major issues with this platform. I’m truly heartbroken as I think this is the best IDE I’ve used thus far. If it’s truly this expensive to run now, I think I’ll be leaving soon.

1 Like
31

Any other issues I can share with the team? Sorry to hear this - we are working to make Cursor better, more reliable, and more cost efficient :folded_hands:

2 Likes
32

I’ve seen “the model made no changes to the file” a few times in a row after 1.3 update. request id for example: b7f0b0b7-8d49-48ba-a789-12d07588b30d , this is sonnet 4 thinking

33

For me, the alwaysApply: true rules stopped working. They weren’t being injected into the context. When I reverted to 1.2, it started working again.

1 Like
34

I discovered a new feature in 1.3. There is a new side panel on the left about agents. It is opened via the firstmost icon to the left of the File menu (I’m on linux).

1 Like
35

jupyter workflow is completely broken by latest release: link
Please fix asap

36

Hey, thanks for the report. I believe we’ll fix this soon.

1 Like
37

Hi! This issue has not been fixed in the latest release and the cursor is extremely inconvenient to use

39

image
image608×303 6.25 KB

I don’t have Early Access, why I got updated to 1.3 too?

40

I’m genuinely confused about the release of the new version of Cursor. Why not do what other companies have done? for example, display a dialog clearly listing what will change (or provide a button to open a webpage outlining the changes and explaining the purpose).
Cursor is a great product, but all the issues stem from poor communication - from pricing to features. :face_exhaling:

9 Likes
41

Get your release strategy fixed, so annoying.

42

as reported by ‘What is new in 1.3.0? - #26 by nickz22’ on the previous thread, today when opening cursor v1.3.0 (Windows), the ‘manual mode’ is missing from cursor chat drop down.
Quite frustrating as that is the mode i use the most, and not sure how to re-create it using ‘custom modes’. My update access is as always been set to ‘default’.

1 Like
43

I hope this issue will be fixed in 1.3

44

There was unfortunately an issue with some deployment logic that cause a small portion of users to get upgraded to the Early Access release without having it enabled.

For anyone who got caught by this, we apologise. You can resolve this simply by redownloading and installing Cursor from our downloads page:

For any other issues not already reported / fixed, please continue to report them here and the team will get back to you soon!

45

image

This new version can’t edit files, the edit command seems to be confused with the actual path. Reverting to a previous version fixed this.

46

Has the 1.3 beta been withdrawn?

image
image1730×254 57.9 KB

47

Wow! I completely second this! Honestly, I haven’t read a more accurate and thorough summary of the issues anywhere. You nailed every frustration I’ve had with Cursor lately.

This is exactly what needs to happen if they want to keep long-term users like me. Only with changes like these would I seriously consider renewing my subscription next month.

Thanks for putting it so well!