Composer and Claude-3.5-sonnet stopped working (Pro)

Hello,

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’d appreciate your help on this, thanks!

Cursor Version:

Version: 0.40.0
VSCode Version: 1.91.1
Commit: 0f6d62072f1bd060caf2876ac639b7d9541add00
Date: 2024-08-22T04:12:20.364Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0
5 Likes

@shaoruu Hi Ian, any chance you could take a look at this?

Not having access to Claude3.5-sonnet really decreases the usefulness of Composer. Claude Sonnet is so much better than gpt4o at Rails tasks.

I’ve also checked the Cursor Developer Tools console - no error messages.

Thanks for your help!

1 Like

Hi @alex235,

Do you have Anthropic API keys turned on? If so could you try turning them off and let me know if that fixed the issue?

Thanks!

Thanks, I tried this but got the same error message.

Can I ask, why does this message appear next to my Anthropic API Key??

I have Cursor Pro and I do want to use my own Anthropic API keys when using composer. Is this not possible anymore?

I swear I was using this feature a few days ago, before the latest Cursor version was released.

Thanks for your help.

1 Like

Also, every 15-20 minutes this MacOS permissions dialog appears. Even though I click Allow, it keeps coming back.

Could you please clarify which other apps Cursor has access to?

Screenshot 2024-08-25 at 09.56.34

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”.

2 Likes

Hi @alex235 ,

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.

Screenshot_1

1 Like

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/.

I’m on macOS Sonoma 14.3

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.

Version: 0.40.1
VSCode Version: 1.91.1
Commit: 58b91712431381a1b75817cd3437cee35dddcb30
Date: 2024-08-24T02:52:24.035Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631

image

Is there a solution? I cannot use Composer because I have Anthropic api key enabled…

Composer isn’t working with your API keys.