Mainframe and Legacy App Automation: Why Traditional RPA Fails and Computer Use Agents Succeed
Legacy systems and mainframes power the core of many enterprises. Yet automating them is painfully slow. Traditional bots get stuck on every UI change, and standard operating procedures often sit untouched because no one can build a reliable bot to follow them. The result is a growing maintenance backlog and a backlog of unautomated work. Computer use agents offer a different approach: they see the screen, act like a human, and follow SOPs as written. This shift moves automation from brittle bots to durable systems that adapt to change.
Why RPA breaks here
RPA tools like UiPath, Automation Anywhere, and Blue Prism automate by binding to UI selectors, XPaths, and object IDs. When a legacy application updates its layout or a mainframe screen changes, those bindings break. The bot halts and a developer must rebuild the flow. For high-volume, stable backend tasks, this rebuild cost can be acceptable. For the long tail of changing screens and exception-heavy workflows, the cost is prohibitive. Industry estimates suggest that more than half of RPA maintenance time is spent on just this kind of change management. In many organizations, the backlog of broken bots grows faster than the team can rebuild them.
What changes with computer use agents
- ●Survives UI changes without a rebuild
- ●No brittle selectors or XPaths needed
- ●Recovers from exceptions instead of halting
- ●Follows SOPs written in plain English
- ●Works on legacy apps, mainframes, Citrix, and virtual desktops
RPA binds to brittle selectors. Computer use agents see the screen and adapt.
How to move without the risk
You do not need to replace all RPA at once. Start with one high-pain process that lives on a legacy system or a Citrix virtual desktop. Document the current process as a standard operating procedure in plain English. Use a computer use agent to pilot the automation. Measure the impact on time, cost, and uptime. If the agent succeeds, expand to similar processes. Where RPA still makes sense, high-volume, stable backend tasks, keep it. The goal is to build a portfolio of durable automation that complements what you already have, rather than replacing it all in one leap.
The path to durable mainframe and legacy automation starts with a single pilot. See how a computer use agent can follow your SOPs and adapt to changing screens. Book a demo with the Coasty team to explore what this looks like for your workflows. https://cal.com/coasty/15min