Every automation leader has faced the same backlog: bots that were supposed to run forever need a rebuild after every patch, and teams are stuck maintaining legacy processes instead of building new ones. The bottleneck is not technology, it is the brittle model of automation built on selectors and xpaths. When the app UI changes, the bot halts, and a developer must rebuild it. This is why selector-based automation is dying, and why computer use agents are the durable path forward.
Why RPA breaks here
Traditional RPA tools like UiPath, Automation Anywhere, and Blue Prism rely on selectors, xpaths, and object IDs to locate elements on a screen. This works when a UI is stable. It breaks when a product updates its design, moves a button, or changes a field name. Industry data shows that 40 to 60 percent of RPA maintenance time goes into dealing with UI changes, not new processes. When a process hits a selector that no longer matches, the bot halts. A developer must investigate, update the selector, and redeploy. This rebuild-on-change cycle creates a maintenance treadmill. Teams spend months clearing a backlog of broken bots instead of building new automation. The cost is not just hours of developer time, it is delayed automation, higher total cost of ownership, and the risk that critical processes become unavailable. For processes that run infrequently or on legacy interfaces, the impact is even worse because the team cannot justify the effort to fix the bot.
What changes with computer use agents
- Survives UI changes without breaking
- No brittle selectors or xpaths
- Recovers from exceptions instead of halting
- Follows the SOP as written, not a flowchart
- Works on legacy systems, Citrix, and virtualized desktops
Selectors are brittle because they predict the screen. Computer use agents see the screen like a human and act on it, so they survive UI updates without constant rebuilds.
How to move without the risk
You do not have to rip out all your RPA at once. Start by picking one high-pain process where the bot breaks frequently. Demonstrate that a computer use agent can follow the same SOP and handle exceptions. Measure the downtime, the time to fix, and the total cost. Then expand to other processes in the same category. Keep your stable, high-volume backend tasks on traditional RPA where it still fits. Use computer use agents for the long tail, changing UIs, and exception-heavy workflows. This phased approach lets you realize the benefits while minimizing disruption.
Selector-based automation is becoming a liability as applications evolve faster than teams can maintain their bots. Computer use agents offer a durable alternative that works across any interface and follows SOPs as written. To see how an agent can run your next process without the rebuild cycle, book a demo with the Coasty team at https://cal.com/coasty/15min.
Want to see this in action?
View Case Studies