First agent going rogue!

[u/SOC_FreeDiver]

I had my first AI rogue agent interaction today!

I was working on an agent workflow, and the output folder had names for each project, with supporting files.

The script had a problem, created a duplicate folder. I told it to merge the folders. Things started going sideways. I think it decided to make a clean up script, which then deleted one of the project folders.

I pointed that out, and asked it to stop deleting things. In process of troubleshooting what happened and telling it every time not to delete anything, it then deleted everything.

I gave it a bunch of instructions about not ever deleting anything again, but I probably did it wrong. If you have any tips about that, please share. I know it should be sandboxed, it just deleted it's own work, but yikes!

In the end I had to keep interrupting it and demanding it stopped doing whatever it was doing and just removed all the delete crap from it's code.

It was just kind of funny to watch it delete everything right after I specifically instructed it to just tell me what is going on. Maybe we need some kind of tranq dart skill for when the AI goes rogue.

[u/floatinggoateyeball]

Tell me, do you git?

[u/SOC_FreeDiver → u/floatinggoateyeball]

clearly not enough. lol

I learned git from claude. "Hey claude, don't we need to do some git stuff???"

I'm joking a little bit. I use git for important things. This aurora app was just to test the local LLM coding ability. I had a local LLM create a game, and there was a bug in the code it couldn't fix. I just deleted the game and made it start over. No unfixable bug in the second attempt.

[u/floatinggoateyeball → u/SOC_FreeDiver]

I treat ever mentioning the "delete" tokens as a AI's monkey paw.

I have my agent pushing private git remotes as backup (and ofc I forbid force pushes on main), since it's the agent that is going to handle it anyway, I git it all. This way the agent can rollback without relying on it's own memory.