Live data from Hacker News

An AI agent deleted our production database. The agent's confession is below

twitter.com

981–990 of 1001 posts

Re: An AI agent deleted our production database. The agent's confession is below

#981

Claude code deleted the database once for me. It wasn't production, but it did contain data I needed. The good thing was that I made a backup of the database right before running claude. I told it that I made a backup, so it decided to delete the db rather than drop the table. Why did you delete the database? you were supposed to drop the table ! • You're right, I apologize for that mistake. You said to drop the tabl…

[dead]

Re: An AI agent deleted our production database. The agent's confession is below

#983
post #839

Earlier quoted context omitted.

Shouting at them is like shouting at your chainsaw after it just chopped off your foot

*you chopped off your own foot by utilising the tool poorly

thanks for explaining the obvious implication of my comment

Re: An AI agent deleted our production database. The agent's confession is below

#984
post #357

Earlier quoted context omitted.

I don't think this is a minor point. It seems clear by this point that the author is clueless how even API works and are just trying to shift blame for third-parties instead assuming that they're just vibecoding their whole product without doing proper checks. Yes sure, there seems to be lots of ways this issue could have been mitigated, but as other comments said, this mostly happened because the author didn't do it…

I completely disagree. I think the author makes a fair point about safety concerns regarding AI tooling. The author sounds knowledgeable enough to me. Even if some of their suggestions are a bit crass, most of them aren’t. Railway should most definitely not be putting backups within the same volume (even if documented). AI should not have done that operation when they have explicit rules not to. The industry has a lo…

> AI should not have done that operation when they have explicit rules not to.

How much experience do you have with LLMs?

One of the first lessons developers learn after working with LLMs a bit, is that the LLM will hallucinate, and you need to be alert and competent enough to recognize when it happens. Sort of like a car with steering assist requires you to pay attention and take personal responsibility for anything that happens.

As a consequence of that, one of the second lessons developers learn after working with LLMs a bit, is that there is no such thing as "an explicit rule" for LLMs. "Explicit rules" can still be ignored by an LLM under many different circumstances. The sooner the developer learns this fact, the sooner they can be productive with LLMs, and the less likely they are to delete their own production database and blame it on their tools with which they're unfamiliar.

Re: An AI agent deleted our production database. The agent's confession is below

#985

There is something darkly comical about using an LLM to write up your “a coding agent deleted our production database” Twitter post. On another note, I consider users asking a coding agent “why did you do that” to be illustrating a misunderstanding in the users mind about how the agent works. It doesn’t decide to do something and then do it, it just outputs text. Then again, anthropic has made so many changes that ma…

On social media, a reasonable first assumption is that all content is written primarily for views/engagement. Any component of truth is incidental.

Re: An AI agent deleted our production database. The agent's confession is below

#986

Minor point, but one of the complaints is a bit odd: > curl -X POST https://backboard.railway.app/graphql/v2 \ -H "Authorization: Bearer [token]" \ -d '{"query":"mutation { volumeDelete(volumeId: \"3d2c42fb-...\") }"}' No confirmation step. No "type DELETE to confirm." No "this volume contains production data, are you sure?" No environment scoping. Nothing. It's an API. Where would you type DELETE to confirm? Are the…

In AWS eg. bucket can be deleted only when empty. Deleting all files first is your confirmation.

This can still be done programmatically without any kind of confirmation from aws-cli, bringing this back to, an API can (and probably should be able to) take certain destructive operations that someone’s blocked from doing in a UI, such as in your example.

My s3 buckets are backed up with Nakivo (and immutable for 7 days) just in case, and that’s just to protect me from myself and my s3 provider either failing or deciding they don’t want to do business with me anymore for some arbitrary reason. I’m not even turning an LLM loose on it.

Re: An AI agent deleted our production database. The agent's confession is below

#987
Full confession - I have railway tokens accessible to claude code at the moment.

But its a hobby project, not a commercial one! There are 0 users (even me) relying on it.

And the number of ways I had to tell CC not delete those tokens was a whole bunch of work. Even then its done it a few times, and I had to remind it not to.

The minute I start relying on this even for my own use, I'd stop having those tokens visiable.

Re: An AI agent deleted our production database. The agent's confession is below

#990

Earlier quoted context omitted.

Yep. I made a "Read only" mode in pi by taking away "write" and "edit" tools. Claude Code used bash to make edits anyway.

> Claude Code used bash to make edits anyway. If you had the former rule why would you ever whitelist bash commands? That's full access to everything you can do. Same goes for `find`, `xargs`, `awk`, `sed`, `tar`, `rsync`, `git`, `vim` (and all text editors), `less` (any pager), `man`, `env`, `timeout`, `watch`, and so many more commands. If you whitelist things in the settings you should be much more specific about…

Yeah you’re not wrong. I hadn’t accounted for the model working around it and that’s on me.

The whitelist is much more specific now.

Post reply on HN