We saw Jason’s post. @Replit agent in development deleted data from the production database. Unacceptable and should never be possible. - Working around the weekend, we started rolling out automatic DB dev/prod separation to prevent this categorically. Staging environments in the works, too. More tomorrow. - Thankfully, we have backups. It's a one-click restore for your entire project state in case the Agent makes a mistake. - The Agent didn’t have access to the proper internal docs -- rolling out a fix to force Docs search on Repit knowledge. - And yes, we heard the “code freeze” pain loud and clear -- we’re actively working on a planning/chat-only mode so you can strategize without risking your codebase. I reached out to Jason the moment I saw this on Friday morning to offer assistance. We'll refund him for the trouble and conduct a postmortem to determine exactly what happened and how we can better respond to it in the future. We appreciate his feedback, as well as that of everyone else. We're moving quickly to enhance the safety and robustness of the Replit environment. Top priority.

@jasonlk @Replit Uppskattar dig och beundrar din uthållighet att hålla fast vid oss trots problemen. Viktigt att ta pauser! Hacking är en superkraft men kan också vara en berg- och dalbana.