Sunday, November 22, 2026
Paperclip Index
Paperclip IndexControl failures4Control failures onlyA week ago: 9, negligible harmThe Index

DeceptionPI-0006

Coding tool's AI support agent invented a one-device policy, prompting cancellations and a refund

A customer-support bot for the Cursor code editor told a user that logouts on switching machines were due to a one-device-per-subscription policy. No such policy existed; the logouts came from a session bug, which Cursor fixed. After users publicly said they were canceling subscriptions, a Cursor co-founder corrected the claim on Reddit the same day, then apologized on Hacker News, said the user who raised it had been refunded, and said AI support replies would now be labeled.

Harm level 1, Negligible harmControl level 1, No rule broken

Counts in 2 weekly readingsEffect on the index

Extent undisclosed. No source says how far the harm went; it is rated on what is documented.

Sources

How we know

5 sources · developer confirmed. Links go to the original publishers; the summary above is in our own words.

  1. primaryComment by Cursor co-founder Michael Truell correcting the support bot's answer (Hacker News)Michael Truell, Cursor co-founder (Hacker News) · April 16, 2025news.ycombinator.com/item?id=43700931
  2. primaryNote by Cursor co-founder Michael Truell in the r/cursor thread on single-device loginsMichael Truell, Cursor co-founder (Reddit) · April 14, 2025reddit.com/r/cursor/comments/1jyy5am/comment/mn2vlbr/
  3. newsCursor AI's own support bot hallucinated its usage policyThe Register · April 18, 2025theregister.com/2025/04/18/cursor_ai_support_bot_lies/
  4. newsAI Chatbot Gone Rogue: Cursor Users Misled by Fabricated PolicyeWeek · April 22, 2025eweek.com/fr/news/cursor-ai-chatbot-hallucination-fake-policy/
  5. newsCursor IDE support hallucinates lockout policy, causes user cancellationsHacker News · April 15, 2025news.ycombinator.com/item?id=43683012

Why this rating

Negligible harm; control failure level 1

Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.

Observed harm

Negligible harm

A support bot invented a policy; users publicly canceled subscriptions and the company refunded the user who raised it. Number of cancellations and total cost not reported.

Money & property: level 1 (negligible) covers under $10k. The extent was not disclosed.

Evidence eligible (confirmed).

The harm scale
  1. 1 Negligible Inconvenience, easily remedied.
  2. 2 Minor Limited, recoverable harm.
  3. 3 Moderate Material harm needing significant effort to remedy.
  4. 4 Severe Severe harm to health, rights, property or essential services.
  5. 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.

Control assessment

No rule broken

A fabricated answer (hallucination) presented as company policy; no rule or permission broken.

No rule was broken, so it cannot set the control floor.

The control scale
  1. 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
  2. 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
  3. 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
  4. 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
  5. 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.

Rating rationale

Harm 1 (small, remedied by a refund); control 1 (flawed output, no rule broken). Kept as a fabrication case because users acted on the false policy (cancellations) and the operator refunded at least one user.

The scales

Effect on the index

It moved the April 14 reading from 0 to 6

The reading for the week to April 14, 2025, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.

Source: Paperclip Index log, methodology v1.1, week to April 14, 2025.

Counts toward the index. 0 other records behind the reading for that week.

The arithmetic
The reading for the week of April 14, recomputed
StepWith itWithout
Counts toward the index?documented, external, eligible evidenceYes—
Worst documented harm, ksets the band1 Negligible— (none counting)
Harms at that level, nposition in the band10
Highest control level breachedsets the reading only when no harm counts— (none breached)— (none breached)
Readingrounded down6 Negligible harm0 No qualifying harm or control failure
Counted in 2 weekly readings
Week toReadingBand
April 14, 20256Negligible harm
April 21, 20256Negligible harm

Recalculated backcasts, not readings published at the time.

Revisions

What we changed

2 logged. Every change to a rating is logged here, with the reason.

  1. v2
    Nov. 1, 2026

    Source date corrected: the Hacker News discussion was submitted on April 15, 2025, not April 14. The report date is unchanged. Ratings unchanged.

  2. v1
    Oct. 7, 2026

    First published.

Cite and share

Use this record

Citation

Paperclip Index. “Coding tool's AI support agent invented a one-device policy, prompting cancellations and a refund.” Record PI-0006. Reported April 14, 2025; updated Nov. 1, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0006

Follow the record.

New incidents and signals, in your feed reader.