• 0 Posts
  • 56 Comments
Joined 9 days ago
cake
Cake day: August 7th, 2026

help-circle








  • No, not at all, and I’m not sure how that could be the conclusion you came to from my post.

    AI should never be touching prod systems without extreme safeguards/permissions set by the systems that they are accessing. Give it a read only db user account. Give it write access to some tables, but no delete/truncate. No AI should be able to run bash commands on production systems by itself without proper safeguards. That’s a failure of the users if it can.

    Systems and software that was built by AI are fine to go into production environments after they’ve done through the regular pipeline of local testing, peer review, QA, unit tests, integration tests, test environment, stage environment, etc.

    You never just give AI unfettered access to production systems to do whatever it wants, just like you don’t give a junior dev that access. People that aren’t “smart or educated enough” won’t have that access either - and again, if they do that’s a gigantic failure by the people that are.


  • When you’re doing local stuff that can’t do any damage due to the existence of things like source control, recycle bin, backups, etc sure, hit that button and let it fly.

    Anything more important though, no - and every one I’ve used specifically warns you against it and that you should check its work. Claude, codex, copilot, grok, cursor, etc all do it.

    Also you can do things like allow all work in a certain folder without asking permission again, if that folder is one you have no sensitive/important data in for example. Claude code will give you this option every time it accesses a new folder in a chat for example.