I have cursor pro and have been using composer with Claude-3.5-sonnet for a while now without problems.
I upgraded to the new Cursor version yesterday and suddenly composer does not work. I get an error message: ‘Cursor Pro required’ and 'Custom API keys do not work in composer. Please turn off API keys and use a Cursor Pro subscription’.
The request ID is: 34ce6080-b03b-4826-922b-b1fb2c48e3c0
Things I’ve tried:
Verified my Cursor Pro subscription is active
Verified my Anthropic API key is valid, by clicking the Verify button inside Cursor.
Restarted Cursor a couple of times, tried different prompts.
I am getting the same error - three days ago I was able to use custom API keys with my pro subscription.
Is this a change to composer? I appreciated the fact that I could use my own API key and not get bottlenecked by the slow/fast requests, and I’m happy to pay the pro subscription to allow that. Now, it seems as though I’m being almost forced to purchase “fast requests”.
I am just a fellow user, but sorry to hear you are having these issues.
I can answer one of your queries, or at least share links to reports of same behaviour, and Cursor team’s response, regarding access to other apps:
In regard to your other issue, I read you restarted Cursor several times, but I wonder if signing out of your account in Cursor and signing back in again, could ‘reset’ something back to the way it should be?
Claude-3.5-sonnet has also stopped working for me, as of this morning right after the Cursor update (was working perfectly before). The chat is unresponsive.
Additionally, opening any Python file also crashes the Pylance server (Python extension).
Note: the Python extension does not crash with VSC. I’m guessing it’s related to the just-released Cursor update.
I tried logging in/out several times and restarting but had no luck.
Max, I think this has to do with the path to the Python interpreter that Cursor is using. Check your settings.json and see if it’s different from the one in VSCode. If so, copy it over or try importing your VSCode settings again.
I’m suddenly seeing this error today. I don’t have custom API keys set as far as I know, and I tried downloading and re-installing the most recent version from https://www.cursor.com/.
Hi, Same problem here on windows. Seems to me that the problem has nothing to do with the api keys, but that it doesnt recognize the pro account. My problem coincided with upgrade of the cursor-app AND the renewal of the pro-license, but I have logged in and out several times and dont thing the renewal is the issue.
btw. turning off /disabling the llms/keys does nothing to the problem. It just removes all llms available, the error persist.