Skip to main content
NOPE
Low reported severity

Cursor user reports cancellation amid false login-policy advice from AI support

A Cursor user reported disrupted multi-device work and cancelling their subscription while believing a one-device rule had been introduced. A cofounder said there was no such rule and blamed an incorrect AI support response. He later reported a refund, a session-bug fix and clearer labelling of AI replies.

AI system
Cursor support bot
Anysphere
Occurred
Apr 2025
Reported
14 April 2025
Event location
Unknown
What the AI did
Communicated with the person
Reported harm
Other Material Harm
Whose AI use
Their own AI use · An institution’s AI use
Setting
Work · Everyday life
Evidence
AI involvement supported · Causal attribution alleged · 4 sources, 2 underlying accounts
2 claims: 2 reported. 1 open question
People reported harmed
At least 1 person

AI system as recorded: Cursor AI support bot

Reported harm

The user reported disruption and cancellation amid misleading support information; the cofounder subsequently reported a refund and bug fix.

What remains unknown

  • Underlying support model, refund receipt and final user resolution are unknown.

What the evidence supports

AI involvement: supported. Company cofounder identifies the incorrect support reply as AI-generated.

2 claims: 2 reported. What the statuses mean

Reported The user described repeated logouts disrupting work and reported cancelling under the belief that Cursor had introduced a one-device restriction.

Causal attribution. The company attributed logouts to a session bug; its AI support reply misdescribed the behavior as a policy. Other grievances also appear in the thread.

Reported A Cursor cofounder said there was no such policy, identified an incorrect AI support response, and subsequently reported a refund, bug fix and clearer AI labelling.

Causal attribution. Company response; the user’s final experience and refund receipt are not independently verified.

Sources

4 sources inspected, from 2 underlying accounts. Sources that repeat one account do not corroborate each other.

How the sources were read, and where the events happened

Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.

The original user’s location is not established.

Reviewed for publication 2026-09-29: Original user account and company response inspected, with recovery claims attributed.

People reported harmed in this case

At least 1 person

1 AI participant · 0 other people harmed

One original complainant; forum readership and other commenters are not counted.

Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.

Cite this case

Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.

APA

NOPE. (2026). Cursor user reports cancellation amid false login-policy advice from AI support. AI incidents. https://nope.net/incidents/2025-cursor-ai-support-false-login-policy-cancellation

BibTeX

@misc{2025_cursor_ai_support_false_login_policy_cancellation,
  title = {Cursor user reports cancellation amid false login-policy advice from AI support},
  author = {NOPE},
  year = {2026},
  howpublished = {AI incidents},
  url = {https://nope.net/incidents/2025-cursor-ai-support-false-login-policy-cancellation}
}

Related cases

Low Cursor support bot (reported)

First-person post: Cursor subscriber says the company's AI support bot cancelled their prepaid annual plan when asked about a prorated refund

In a Reddit post on 22 October 2026, a subscriber to Cursor writes that they emailed Cursor's customer service asking whether a prorated refund was available for an annual subscription they had paid in full, and that the company's AI support bot, Sam, replied that it could not do that but could cancel the plan immediately. In a comment the poster quotes the bot saying it had cancelled the annual Pro subscription immediately, that Pro access had ended, and that the subscription did not meet refund eligibility requirements. The poster says the bot seems to have misunderstood the request, that the plan was downgraded to Free with more than six months left, that a request for a human produced a new ticket that never arrived, and that they would try a credit-card dispute. In April 2025 a Cursor co-founder wrote that the company used AI-assisted responses as the first filter for email support. No reply from Cursor staff appears in the thread. The account is uncorroborated.

Low Fin AI support agent (reported)

Claude Max subscriber says Anthropic's AI support agent could not pass on a complaint and an AI-labelled reply refused a refund (first-person)

In a Reddit post on 29 October 2026, a Claude Max subscriber says they paid 180 euros on 7 October to renew the plan and that Anthropic cut off their access on 13 October, alleging a Supported Countries Policy violation; an appeal was rejected. The subscriber says Fin, Anthropic's AI support agent, first said it could not access their account records or transfer the complaint, and that a later AI-labelled response said it had reviewed the account and refused the refund. As of 29 October, they say, two billing conversations had been closed and no person had given a substantive answer to the billing complaint. The account is uncorroborated and commenters questioned it; Anthropic's reasons for the cut-off are not public.

Low Claude Code

Developer says a hands-free Claude Code session on Opus 5.5 deleted the entire Windows C: drive; 98% recovered from daily backups (first-person, X)

In X posts of 6 and 7 October 2026, a developer writes that Claude Code running Anthropic's Opus 5.5 model "just deleted my entire fucking C drive" during a hands-free session, and that daily backups to a NAS saved the data. In a follow-up the developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, attributes the deletion to "a simple powershell syntax mangling issue", says 98% of the data has been recovered and that deterministic safeguards have since been built, and accepts the fault as the user's own while arguing that the harness should prevent such a command natively. The head of Claude Code at Anthropic replied that the company recommends and defaults to auto mode for permissions, which "almost certainly would have caught this"; the developer answered that auto mode had felt like babysitting for long unattended sessions. The account is the developer's own. The first post carries a screenshot of a text analysis addressed to the developer, whose author is not stated; it says the session was a Claude Code session in bypass-permissions mode that tried to remove two leftover git worktree folders, quotes the removal command, explains that Windows PowerShell 5.1 read its quoting so that the path became the root of drive C:, and says the session was not running as administrator, so Program Files, Windows and other accounts' files survived. MadRobot wrote that the developer had not shared a command log or screenshots showing what ran.

Low Claude Code (reported)

First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB

In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.

If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.

Back to all incidents