# One in seven people who wrote about their own use of Cursor in the last five weeks complained about its support, eight times the field

*From 12 October to 15 November, 14.2% of the people who wrote about their own use of Cursor complained about its support, against 1.8% for every other coding agent. That is more than double Cursor's own rate in the six weeks before. Many said a ticket was ignored or left unresolved, or that they could not get past the support bot to a person.*

Capability case, Cursor. By Feedback Bench, 19 November 2026. Feedback Bench 1.1. Posts 31 August 2026 to 15 November 2026. Web: https://feedbackbench.com/coding-agents/#/articles/one-in-seven-people-who-wrote-about-their-own-use-of-cursor-in-the-last-five-weeks-complained-about-its-support-eight-times-the-field

In late October a Cursor user on X wrote:

> A week without a human reply after Cursor AI support said 1–2 days. My $200 Sept 15 Ultra renewal went unused; my refund appeal is still unresolved. Paying users deserve a real review and clear answer.

[A user on X, 2026-10-22](https://x.com/potato_zgzg/status/2113291747866628371)

Of the 3,070 people who wrote about their own use of Cursor between 12 October and 15 November, 436 complained about its support. That is 14.2%, or about one in seven. Among people who wrote about their own use of any other coding agent, it is 1.8%.

Every other coding agent with a sizeable following is at 3.3% or under. Google Antigravity, the other large AI editor, is at 0.9%.

**Exhibit 1: Complaints about support, by coding agent, from 12 October.** Share of people who wrote about their own use of each agent from 12 Oct to 15 Nov and complained about its support. Cursor is 14.2%, 7.9 times the 1.8% for people who wrote about their own use of any other coding agent.

|  | Share of people |
|---|---|
| Cursor | 14.2% (436 of 3,070) |
| Devin | 3.3% (19 of 581) |
| OpenCode | 2.1% (85 of 4,057) |
| Claude Code | 1.9% (192 of 10,149) |
| GitHub Copilot | 1.6% (7 of 451) |
| Amp | 1.2% (8 of 645) |
| OpenAI Codex | 1.2% (94 of 7,788) |
| Google Antigravity | 0.9% (43 of 4,720) |
| Zed | 0.6% (2 of 315) |
| Pi | 0.2% (1 of 540) |
| All other coding agents | 1.8% (488 of 27,309) |

*12 Oct to 15 Nov 2026. Counts are people, not posts. Anyone who wrote about their own use of Cursor is removed from every other row.. Agents that fewer than 200 people wrote about from their own use in these weeks are left out: Cline (5 of 104), Warp (3 of 61), Factory (7 of 169), Augment Code (0 of 5), Kiro (23 of 190), Grok Build (0 of 7).. Source: Feedback Bench labels, build of 16 Nov 2026.*
Share of people who complained about support, 12 October to 15 November, for coding agents with a sizeable following. Cursor 436 of 3,070 (14.2%), every other coding agent together 488 of 27,309 (1.8%).

Those weeks began with a change to Cursor's plans. On 12 October Cursor [introduced The X Subscription](https://forum.cursor.com/t/introducing-the-x-subscription/174450), one plan for Grok, Grok Bot, Cursor and X Premium. The post asked users to send anything about their own account, "a charge, a plan that didn’t carry over, the wrong account linked," to support by email at support@x.ai.

## Cursor's support complaint rate more than doubled in mid-October

In the six weeks before 12 October, 352 of the 5,697 people who wrote about their own use of Cursor complained about its support. That is 6.2%, already 3.5 times the field's 1.7%.

Before 12 October, Cursor's weekly rate was between 4.0% and 6.9%. In each week since, it has been between 11.9% and 17.6%. The field stayed under 2% throughout.

**Exhibit 2: Cursor's weekly rate of support complaints rose in the week of 12 October and stayed higher.** Weekly share of people who wrote about their own use of Cursor and complained about its support, and how many times the field's rate that is. It was 4.0% to 6.9% in the six weeks before 12 October and 11.9% to 17.6% in each of the five weeks from then.

|  | Share of people |
|---|---|
| 31 Aug | 4.0% (45 of 1,117), 4.0 times the field |
| 7 Sep | 5.5% (73 of 1,325), 4.6 times the field |
| 14 Sep | 5.5% (67 of 1,208), 4.0 times the field |
| 21 Sep | 5.6% (74 of 1,331), 4.3 times the field |
| 28 Sep | 5.1% (56 of 1,094), 3.6 times the field |
| 5 Oct | 6.9% (66 of 959), 4.3 times the field |
| 12 Oct | 11.9% (114 of 956), 9.1 times the field |
| 19 Oct | 17.6% (133 of 755), 9.2 times the field |
| 26 Oct | 13.1% (90 of 688), 9.2 times the field |
| 2 Nov | 12.6% (79 of 627), 10.2 times the field |
| 9 Nov | 12.5% (64 of 512), 7.3 times the field |

*31 Aug to 15 Nov 2026, all channels. Counts are people, not posts. A person is counted in a week when one of their complaint posts, and one of their posts about their own use of the agent, falls in that week. The field is everyone who wrote about their own use of another coding agent that week, with anyone who wrote about their own use of Cursor in the window removed.. Source: Feedback Bench labels, build of 16 Nov 2026.*
Weekly share of people who wrote about their own use of Cursor and complained about its support, with the rate as a multiple of the field. Between 4.0% and 6.9% in the six weeks before 12 October, and between 11.9% and 17.6% in each of the five weeks since.

## Many said a ticket was ignored or left unresolved

Many of the 436 said a support ticket was ignored or left unresolved. They often give a ticket number and a count of days.

## One in four said they could not get past the bot to a person

117 of the 436 said they could only reach Cursor's AI support assistant, which users call Sam, and not a human. That is 26.8%. Some describe follow-ups closed as duplicates. One user on a $100 plan wrote that "[Every follow-up gets auto-closed by a bot](https://x.com/adamlachman21/status/2119514856131072372)." Another asked for a person to take over a refund:

> Please have a human billing specialist take over ticket T-J20732. Sam keeps reporting refund errors and cannot arrange human review.

[A user on X, 2026-11-05](https://x.com/chnxunji817317/status/2118162621358858301)

**Exhibit 3: One in four of Cursor's support complainers said they could not get past the bot, from 12 October.** People who complained about Cursor's support from 12 Oct to 15 Nov, by the main thing that went wrong in each post. 117 of 436 (26.8%) said they could not get past the support bot to a person; 78 named a refund and 76 a broken payment or subscription link.

|  | Share of people who complained |
|---|---|
| AI support bot blocks human escalation | 26.8% (117 of 436) |
| Refunds refused or never processed | 17.9% (78 of 436) |
| Payment and subscription linking errors unfixed | 17.4% (76 of 436) |
| Account bans and lockouts without explanation | 4.4% (19 of 436) |
| Bug reports and community contributions ignored | 3.7% (16 of 436) |
| Program applications and promised perks unanswered | 0.5% (2 of 436) |

*12 Oct to 15 Nov 2026. Counts are people, not posts. A person can be in more than one kind. AI agents sorted each complaint post into one kind under the bench's written rules.. Not shown: support tickets ignored or left unresolved. A post that names several problems counts under one, so many posts that mention an ignored ticket sit under another kind and the sort undercounts this one.. Left out: Fits none of the named kinds 27 of 436. 22 of 436 have only such posts.. Source: Feedback Bench labels, build of 16 Nov 2026.*
People who complained about Cursor's support from 12 October, by the main thing that went wrong in each post, leaving out ignored tickets, which this sort undercounts. 117 of 436 (26.8%) said they could not get past the support bot to a person, 78 named a refund and 76 a broken payment or subscription link.

## Some said a refund or a merged account went wrong

Fewer named a money problem. 78 of the 436 said a refund was refused or never processed. 76 said a payment or subscription link broke and stayed broken.

The X Subscription guide to combining accounts, last updated 12 October, says: "A completed unification is permanent. It can’t be undone, and Support can’t undo it for you." On 27 October a Cursor staff member closed a forum thread from users whose Grok Bot setups had disappeared after they combined accounts. The post said the last step of the merge "didn’t complete on our end," that the team was working on a fix, and that "There’s a significant backlog at the moment."

Some say their trouble began when they combined accounts:

> been stuck for days on ticket T-I39419. My Grok Bot won't connect to my account after a failed account merge and my replies keep getting auto-closed as duplicates.

[A user on X, 2026-10-28](https://x.com/StefanCiancio/status/2115454862607466689)

## What this suggests

The posts quoted here ask for a person to look at the ticket and for a clear answer. Where the cause is a known merge failure, a ticket status that says so, gives an expected date and does not close follow-ups as duplicates could help.

## Limits

The rise came from people who had not written about their own use of Cursor before 12 October. Those who wrote about their own use of it in both periods complained about its support at about the same rate before and after. Many of the posts we read tie the trouble to the account merge, Grok Bot or X billing, so some of these people came to Cursor's support about the new plan as much as about the editor.

The timing alone does not show what caused the rise. On X, where most of these complaints are and where people tag @cursor_ai to get help, the rate jumped in the week the new plan arrived. On Reddit the rise was smaller and came a week later, though Cursor is still well above the field there.

Kiro, a smaller AI editor, gets support complaints at a similar rate, but too few people wrote about their own use of it to tell the two apart.

## Sources

- [Feedback Bench, coding agents, build of 16 November 2026, window 31 August to 15 November 2026](https://feedbackbench.com/coding-agents/)
- [How the benchmark works](https://feedbackbench.com/coding-agents/#/method)
- [Feedback Bench, Support, refunds and issue handling](https://feedbackbench.com/coding-agents/criteria/account.support.md)
- [Cursor forum, Introducing The X Subscription, 12 October 2026, read 19 November 2026](https://forum.cursor.com/t/introducing-the-x-subscription/174450)
- [The X Subscription docs, How to unify accounts under The X Subscription, last updated 12 October 2026, read 19 November 2026](https://docs.x.ai/x-subscription/unify-accounts)
- [Cursor forum, All my Grok Bot Disappear, staff post of 27 October 2026, read 19 November 2026](https://forum.cursor.com/t/all-my-grok-bot-disappear/175510/127)
