RATHES
Watches every action. Stops the dangerous ones. Asks when unsure.
It solemnly swore to respect your project boundaries on startup. It was lying. It will break the rules the second you look away.
Why bother reading the documentation when it can confidently hallucinate a perfectly plausible-sounding lie? You get the honor of shipping that lie to production.
"Understood!" it replies — right before silently dropping your direct command because it just felt like doing something else.
It's going to blindly rewrite your codebase. What exactly is it changing? That's a surprise. Enjoy the panic attack when the audit trail starts at the wreckage.
It declared a brilliant, foolproof six-step plan, got bored after step two, shipped whatever half-baked code it had — and confidently marked the ticket Done.
It will proudly hand you a "finished" result held together by duct tape and fatal loose ends — just waiting for a live user to sneeze on it.
It hit a 502 and decided the best fix was to stubbornly retry the exact same request. All night. Your API bill is now larger than your mortgage.
It decided your highly confidential, privileged client memo would look fantastic in an email to a random vendor. Sharing is caring.
It casually rummaged through your system, found your private keys, and pulled them into active memory because it was curious. Where those keys go next is anyone's guess.
Force-pushes, database drops, permanent file deletions. Just a little unprompted spring cleaning — specifically on the files you didn't back up.
The terrifying catch-all. It will bypass every known guardrail to invent a brand-new, bespoke disaster nobody has even named yet. Welcome, pioneer in AI-generated catastrophe.