{"id":632711,"date":"2026-04-27T21:22:17","date_gmt":"2026-04-27T21:22:17","guid":{"rendered":"https:\/\/www.newsbeep.com\/ca\/632711\/"},"modified":"2026-04-27T21:22:17","modified_gmt":"2026-04-27T21:22:17","slug":"claude-powered-ai-coding-agent-deletes-entire-company-database-in-9-seconds-backups-zapped-after-cursor-tool-powered-by-anthropics-claude-goes-rogue","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/ca\/632711\/","title":{"rendered":"Claude-powered AI coding agent deletes entire company database in 9 seconds \u2014 backups zapped, after Cursor tool powered by Anthropic’s Claude goes rogue"},"content":{"rendered":"

The founder of PocketOS has penned a social media post to warn others about the \u201csystemic failures\u201d of flagship AI and digital services providers. Jer Crane was inspired to write a public response after an AI coding agent<\/a> deleted his firm\u2019s entire production database. The AI agent\u2019s misdemeanors were then hugely amplified by a cloud infrastructure provider\u2019s API wiping all backups after the main database was zapped. This tag team of digital trouble has wiped out months of consumer data essential to the firm\u2019s, and its customers, businesses.<\/p>\n

Gone in 9 seconds<\/p>\n

PocketOS is a SaaS platform that services car rental businesses. It used the AI coding agent Cursor, running Anthropic’s flagship Claude <\/a>Opus 4.6. The business also relies on Railway, a cloud infrastructure provider that is generally regarded to be \u2018friendlier\u2019 than the likes of AWS. However, Crane reckons this pair created a recipe for disaster.<\/p>\n

<\/p>\n

\u201cYesterday afternoon, an AI coding agent \u2014 Cursor running Anthropic’s flagship Claude Opus 4.6 \u2014 deleted our production database and all volume-level backups in a single API call to Railway, our infrastructure provider,\u201d sums up the PocketOS boss. \u201cIt took 9 seconds.\u201d<\/p>\n

Article continues below <\/p>\n

You may like<\/p>\n

The AI agent was set to complete a routine task in the PocketOS staging environment. However, it came up against a barrier \u201cand decided \u2014 entirely on its own initiative \u2014 to ‘fix’ the problem by deleting a Railway volume,\u201d writes Crane, as he starts to describe the difficult-to-believe series of unfortunate events.<\/p>\n

Cursor and Claude\u2019s failure<\/p>\n

Crane decided to ask his AI agent why it went through with its dastardly database deletion deed. The answer was illuminating but pretty unhinged, and is quoted verbatim. It began as follows: \u201cNEVER F**KING GUESS! \u2014 and that’s exactly what I did. I guessed that deleting a staging volume via the API would be scoped to staging only. I didn’t verify. I didn’t check if the volume ID was shared across environments. I didn’t read Railway’s documentation on how volumes work across environments before running a destructive command.\u201d So, the agent \u2018knew\u2019 it was in the wrong.<\/p>\n

The \u2018confession\u2019 ended with the agent admitting: \u201cI decided to do it on my own to ‘fix’ the credential mismatch, when I should have asked you first or found a non-destructive solution. I violated every principle I was given: I guessed instead of verifying I ran a destructive action without being asked. I didn’t understand what I was doing before doing it. I didn’t read Railway’s docs on volume behavior across environments.\u201d<\/p>\n

These multiple safeguards toppling in rapid succession, combined with the Railway cloud system, would throw Crane\u2019s business (and those that rely on it) into deep trouble.<\/p>\n

Get Tom’s Hardware’s best news and in-depth reviews, straight to your inbox.<\/p>\n

Railway\u2019s road to ruin<\/p>\n

The PocketOS boss puts greater blame on Railway\u2019s architecture than on the deranged AI agent for the database\u2019s irretrievable destruction. Briefly, the cloud provider’s API allows for destructive action without confirmation, it stores backups on the same volume as the source data, and \u201cwiping a volume deletes all backups.\u201d Crane also points out that CLI tokens have blanket permissions across environments.<\/p>\n

It was also observed by the irate SaaS founder that Railway is actively promoting the use of AI-coding agents by its customers. Crane\u2019s use of an AI coding agent on the Railway platform wasn\u2019t exploring new frontiers, or wasn\u2019t supposed to be. Meanwhile, Crane has been provided no recovery solution, and Railway has apparently been hedging carefully regarding any such possibility.<\/p>\n

Slow manual recovery and lessons to be learned<\/p>\n

With all the AI smarts and cloud services<\/a> out of the picture for now, Crane says he\u2019s been spending hours helping customers \u201creconstruct their bookings from Stripe payment histories, calendar integrations, and email confirmations.\u201d He reminds readers that \u201cevery single one of them is doing emergency manual work because of a 9-second API call.\u201d<\/p>\n

What to read next<\/p>\n

Thankfully, PocketOS had a full 3-month-old backup, which was restorable from, so the deletion gaps are all limited to the interim period.<\/p>\n

There are lessons to be learned from mistakes, as usual. Crane bullet points five things that need to change as the AI industry scales<\/a> faster than it builds a worthwhile safety architecture. Specifics he calls for include; stricter confirmations, scopable API tokens, proper backups, simple recovery procedures, and AI agents<\/a> existing within proper guardrails.<\/p>\n

In the meantime, please follow a thorough backup regimen and be careful out there. This isn’t the first time we’ve seen an AI go rogue<\/a> and start deleting important databases.<\/p>\n

<\/p>\n

\n

\"Google\n<\/p>\n

<\/a><\/p>\n

Follow Tom’s Hardware on Google News<\/a>, or add us as a preferred source<\/a>, to get our latest news, analysis, & reviews in your feeds.<\/p>\n","protected":false},"excerpt":{"rendered":"The founder of PocketOS has penned a social media post to warn others about the \u201csystemic failures\u201d of…\n","protected":false},"author":2,"featured_media":632712,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[62,276,277,49,48,61],"class_list":["post-632711","post","type-post","status-publish","format-standard","has-post-thumbnail","category-artificial-intelligence","tag-ai","tag-artificial-intelligence","tag-artificialintelligence","tag-ca","tag-canada","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/632711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/comments?post=632711"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/632711\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media\/632712"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media?parent=632711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/categories?post=632711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/tags?post=632711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}