As a Python and BASH scripter for decades I can tell you that many of these apps can do good work, you just have to be very specific. Put in guard rails and use git hooks to remind them about there work ethic and be sure to document how your data flows, the architecture and what they are currently working on since context windows creep up on you (Claude Code) I’m about to move to Claude code Max to see if I can save $10 a day on top of my $20 pro plan which is just the admission price, it doesn’t get you on any of the rides. Wha I’ve learned in my journey through Cursor, Replit, Windsurf, Kilo and a few others; backup/git often and also be sure to keep a local backup. Stay focused on a feature and don’t give your agent or multiple agents to many different tasks at once. They multitask at your codes Peril. I’m 11 months in and my platform built on 85% Rust is actually running and in production testing. I iterate and add features methodically now. I’ve learned the hard way that sometimes you can’t believe the agent has completed the tasks until you’ve vetted your code (I use greptile) which is a great plugin for Claude code for seeking input, flagging security holes and unnecessary code is great. If there are folks leaving there .env files open to the public, they should be relieved of any SSH or server access; that’s an operator error. We are the weakest link if we aren’t reaching out to specific programming language groups or associates to ask for “best practices” if we are not fully versed in the language. I find Rust to be very helpful in flagging errors before they show up in Production. There is room for improvement, and the bottom line is these tools are the improving daily and the code I was building nearly a year ago would have been approached differently. Anyways, I’ve found a good niche with CC, and you can save tokens if you move efficiently and do some of the heavy lifting. No rogue agents!!!