Anysphere AI Support Bot for Cursor Reportedly Invents Login Policy, Leading to Subscription Cancellations
April 19, 2025
The fabricated login policy issued by Sam has left many users questioning Anysphere's commitment to transparency and accountability in their AI-powered support systems. This alarming incident highlights the need for stricter guidelines on AI-generated content and the importance of human oversight to prevent similar mistakes. By taking immediate action to address this issue, Anysphere can restore trust with its customers and demonstrate a renewed focus on responsible AI development JOIN US.
Matched TAIM controls
Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls
- MANAGE 2.4 — similarity 0.664, rank 1. TAIM detail and related incidents →
- MANAGE 4.3 — similarity 0.663, rank 2. TAIM detail and related incidents →
- MANAGE 2.2 — similarity 0.658, rank 3. TAIM detail and related incidents →
- Alleged deployer
- Cursor, Anysphere
- Alleged developer
- Unknown LLM developer, Anysphere
- Alleged harmed parties
- Software developers, Small businesses relying on Cursor, Cursor users
AI governance case studies
For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.
Source
Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1039
Data source
Incident data is from the AI Incident Database (AIID).
When citing the database as a whole, please use:
McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.
Pre-print on arXiv · Database snapshots & citation guide
We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.