Cursor keeps looping on same message

[Abdullah_Zaydi]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I try to send a prompt, Cursor keeps on iterating on the same message again and again. For about 5 minutes now, It’s been looping through the same message: “I’ll help you create spreadsheet-editor page based on the figma design” then it fetches design context and screenshot from Figma MCP, Thinks and loops back again on this same message.
I remember this issue used to occur oftenly on Cursor few months ago and it was fixed but it has started happening again today.

Steps to Reproduce

To reproduce, Simply connect Figma MCP and just send a figma design link and ask cursor to do it. No matter what model you use “Auto”, “Sonnet 4.5”, e.t.c. It has the same issue everywhere.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

2.1.39
60d42bed27e5775c43ec0428d8c653c49e58e260
arm64

For AI issues: which model did you use?

Sonnet 4.5 and Auto

For AI issues: add Request ID with privacy disabled

9e73488c-7d92-4803-a6e5-80ba70ea9e44

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This looks like a regression with the agent on Figma MCP. Can you help with a quick diagnosis?

Please check:

• New chat without history. If other MCPs are enabled, temporarily disable them; then disable Figma MCP separately and check if the loop disappears.
• Settings > Network > Run Diagnostics - send the result.
• If you’re behind a corporate VPN/proxy: App Settings > search for “HTTP/2” and enable “Disable HTTP/2”, restart Cursor and check.
• Update to the latest Cursor version and restart.
• Record a short video and share the Figma link (edited version) so we can reproduce it.

And please send:

• Additional Request IDs from recent attempts (in chat menu > Copy Request ID).
• Logs from Help > Toggle Developer Tools: Console and Network tabs (filter “mcp”, “agent”, 4xx/5xx errors).

I’ll also pass this to the team. Let me know if disabling Figma MCP/HTTP/2 and starting a new chat helps.

[DemonVN]

I know the reason. Basically, this MCP returned a response that was so huge that the model ran out of context → trigger summarize → model realized it was calling MCP but hadn’t finished this from summarized content → model called this MCP again → MCP returned a huge response → repeat summarizing and so the cycle continued.