Can not use agent claude-3.7-sonnet-thinking

When using claude-3.7-sonnet-thinking as agent mode in Cursor 0.46.3 and Windows 11.

I am permanently getting the error:

We’re having trouble connecting to anthropic. This might be temporary - please try again in a moment.

Request id: 40356780-f506-4392-98f5-47dbff3c0060

7 Likes

Same issue here, experiencing it on both models as well.

Yes! Similar problems all day. The forum says such queries are still billed as queries. This is not very good. Will there be any compensation? I’ve already had to restart about 50 times today.

3 Likes

Hey, try creating a new session, it might help.

1 Like

Unfortunately, it didn’t help—in the most inconvenient moment, the same error occurred again.

just info, copilot has unlimited usage also available claude sonnect 3.7

The ‘Try Again’ button yields zero results. The ‘Resume’ button completely resets the request. If I could be absolutely sure that these requests aren’t being charged, it wouldn’t be a big issue. But I read messages on the forum and realized that Cursor does charge for them. And that’s very frustrating.

1 Like

As for Copilot, (just for answer to your info =) Codeium is a better option, then Copilot, but they haven’t fully integrated Claude 3.7 yet.

Still, I want to believe in the creators of Cursor—they are definitely among the top AI Agent systems today.

I don’t think codium have unlimited usage AI Sonnet

Only in chat. in composer mode don’t have.

Thank you for your prompt reply. I’ve successfully updated to version 0.46.4, and I’m pleased to report that everything is now working perfectly. I appreciate your assistance.

1 Like


I also updated to 0.46.4, but unfortunately, the issue still persists. =(

Look’s like it is impossible now to switch between modes in context of the same session. Is that intended behavior?

I am not sure if influences but Claude.ai right now has the same limitation

Interestingly, it works in Copilot, but Claude seems to be a nerfed version in Copilot.

1 Like

It keeps happening, besides the Premium requests still get used, it stops midway…

Yes, it happens aparently randomly and consumes the fast tokens…

1 Like

Yes, we definitely shouldn’t have our fast credits used if there is system downtime.

5 Likes

for me if it works its using a credit for each agent action, i.e. read a file 1 credit, update a file 1 credit. so many wasted credits

1 Like

I’m on Version: 0.46.4 (Mac 15.2)
Problem is persisting for me. It’s stuck “generating”. It would be great is one bug didn’t stop you from working on something else while bugs are squashed. I’m pretty much stalled until this works again. Do users pay for requests that lead to no response? Please advise.