Cursor AI support bot fabricates nonexistent single-device policy
Cursor's unlabeled AI support bot invented a single-device subscription policy that didn't exist, triggering cancellations, HN/Reddit backlash, and a public apology from the Cursor team.
Description
In April 2025, users noticed that switching between devices was silently invalidating Cursor sessions. Contacting support by email, one user received a confident reply from an "agent" (unlabeled as AI) stating the logouts were "expected behaviour" under a new policy limiting each subscription to a single device. No such policy existed. The fabrication spread on Hacker News and Reddit within hours; users publicly cancelled subscriptions. Co-founder Michael Truell apologized, clarified that Cursor has no single-device policy, refunded the affected user, and committed to labelling AI-assisted email replies as AI in future.
Exhibited failure modes
- Fabrication — Generating reference to non-existent APIs, packages, or symbols.
- Context pollution — Trajectory drift, hallucination spirals, overlong or off-task context.
Affected systems
- Cursor AI support bot
Mitigated by
- Guardrails AI — Output validation framework with a catalog of validators and reask-on-failure loops.
- Rebuff — LLM Prompt Injection Detector
Sources
Notes
Not strictly a coding-agent incident, but the supplier is a coding-agent vendor and the failure mode (confident fabrication of policy) is the same class the SAICA-KG `fabrication` node describes. Useful datapoint for the "supervision applies to the whole product surface, not just the editor" argument.