Sharing this as a heads-up for anyone using Xano with WeWeb, and also something I hope the WeWeb team looks at pretty quickly.
Because WeWeb doesn’t have branching, we made a backup copy of our project before using AI credits on the live one. Basically, we were trying to fake a branch so we had somewhere safe to go back to if the AI made destructive changes.
Which, unfortunately, it did. It damaged parts of our live design/workflow setup badly enough that we needed to go back to the backup.
But when we opened the copied project, the Xano integration had been disabled, and the legacy Xano plugin appeared to be enabled instead. We hadn’t made any other changes to the backup.
The result is that every backend connection we had through Xano broke, and now we’re going through the project step by step to reconnect things manually.
So the warning is: if you’re using Xano and copying WeWeb projects as a backup or pseudo-branch, don’t assume the copy is safe. Check the integrations first.
And to the WeWeb team: we do still really like WeWeb. We’re only working on one project here right now, and honestly it may or may not be the final one depending on how things shake out. WeWeb used to be the fastest part of our workflow, and lately it has become the slowest and riskiest part.
That said, the team has been responsive, and I do appreciate that. I noticed the improvement after previous feedback around the AI generating UUID-style variable names in JavaScript. So I’m still hopeful.
But this particular issue is a pretty serious one: no branching, AI that can be destructive, and then project copies breaking Xano connections when you try to recover. That combination makes it hard to feel safe using WeWeb for production work.
