I’ve been curious about this AI Copilot approach where you basically describe what you want in plain English and it generates a workflow. On paper it sounds amazing, but I’m skeptical about how well it actually handles the messy reality of web automation.
Like, websites change their structure constantly. Selectors break. Dynamic content loads differently depending on network speed. I’ve read that the copilot can take a description and turn it into a ready-to-run automation, but I’m wondering—does it actually account for these real-world complications? Or does it generate something that works once on a clean test run but falls apart in production?
I’m also thinking about the cognitive load here. Even if the copilot generates 80% of what I need, I still have to understand what it created to debug it when it breaks. So does this approach actually save time, or does it just shift the work from writing to troubleshooting?
Has anyone actually tried this with a real production workflow and not just a demo? What broke first?