Yeah, I kind of agree. The UI before 1st time use is confusing - the button said sth like “Change plan to allow MAX” - which is wrong now. There also was no clear statement from Cursor, just some users claimed it (they claim a lot here).
I’m unable to use the VS Code Marketplace with 1.2.0 and 1.2.1. Setting these values in the product.json file, worked in previous versions. Using these values now and performing a Marketplace search returns no results.
"extensionsGallery": {
"galleryId": "cursor",
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"itemUrl": "https://marketplace.visualstudio.com/items",
"resourceUrlTemplate": "https://{publisher}.vscode-unpkg.net/{publisher}/{name}/{version}/{path}",
"controlUrl": "https://main.vscode-cdn.net/extensions/marketplace.json",
"recommendationsUrl": "",
"nlsBaseUrl": "",
"publisherUrl": ""
},
2 Likes
I would just love if Cursor worked 
The v1.2.1 edit cursorrule always failed.
Version: 1.2.1
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:06:37.704Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
It’s nothing intuitive enough as a tool or function to rely on for contextual awareness etc. It’s much better to utilize the todo_tool so it stays contrsticted and pertained to only what’s created by this tool. I suggest avoiding the memory feature until it gets improved etc. but I understand what you’re saying 
@YuTengjing does this still occur? If its repeatable, could you file a full bug report with a Request ID? (for that please temporarily disable privacy mode so Cursor Team can investigate that one request).
Everything is paid now? We don’t have slow queue anymore? Because every single request that I make is increasing my invoice
@Brunob112 please discuss pricing in a separate thread, this is only about Cursor v1.2 pre release.
that is a limited view of how people use the marketplace.
one basic use of changing the marketplace is when you want to make sure only certain extensions can be used by your team/customers.
another one would be people that actually want to use openvsx as opposed to cursor’s marketplace (I don’t know how it’s actually architected, but I can currently search the openvsx marketplace, cursor is giving a 503. I do not want to create forum threads everytime something goes wrong in cursor’s marketplace)
cursor switching to openvsx as the default, doesn’t negate the need for being able to change the marketplace.
this was working before 1.2, it broke in 1.2 due to updated VSCode base version.
all we need is to be provided with the ability for having a custom product.json at a predetermined path that will be merged with the product.json shipped in the app bundle. this facilitates easy customization of the marketplace.
3 Likes
Official changelog just dropped: https://cursor.com/changelog/1-2
1 Like
Its official
1 Like
Aren’t todos restricted to one chat conversations? They have only one tool - todo_write, no todo_read, so you can’t read todos from previous chats.
This way, the moment you start a new chat window, available memories are better than unavailable todos.
2 Likes
This is correct, however a quick work around is to screenshot the previous “TO DO” and it will update accordingly and will continue where it leaves off. I have been training and using custom commands purely with Claude Sonnet 3.7 Thinking and now it does everything how I want when I want when I ask. Zero issues.
How my 503 Issue cleared
I went down this rabbit hole looking at everything, opened up the browser and debugged the application and saw no real issues.
More than likely what’s happening is you have an old bearer token that is accepting the connection isn’t compatible to the new 1.2 version RLS on the backend? I exited both my Linux server and my local IDE as both of them were having the 503 issue.
After restarting the IDE the issue went away. I think what caused this was that the update popped up and installed, however, I never saw a restarted services so more than likely thats what caused it.
Pure speculation on my end with the information captured.
I was wondering why the 1.2 can do so much then before and in the video i noticed better codebase search my god its insane how much better it is and how fewer errors the agent is making can we put full focus on that area instead of new features ?
3 Likes
Update: (for the issue regarding the Cursor Agent not detecting command completion)
Tried the v1.2.1 today - the issue is still not fixed. I’m sorry I can’t provide request-ids or console logs, as I’m currently rate-limited, and I forgot to do it, when I still could use Sonnet.
1 Like
FYI, in the embeddings performance comparison chart in the v1.2 changelog, the bars for difficulty level 5 do not look correct; the change in bar size is less than the label says, +33.5%. I’d guess that the bars were copy/pasted from difficulty level 4.
@T1000 Since v1.2.0, the settings extensions.gallery.itemUrl is not working anymore, which results the user cannot switch to alternative extension market.
1 Like
There is a serious problem with todo list, and there will be a dead loop, and the completed evil tasks will be loaded repeatedly