Your automation team has a backlog of processes stuck in the queue. The bots work well on a few stable applications, but many workflows live on Citrix sessions, virtual desktops, or legacy systems that never change their UI. When the internal app updates a button or layout, the bots break. When the service changes a field name, the bot halts. The team spends more time rebuilding bots than running them. Meanwhile, the team has documented SOPs that describe exactly what people do, step by step, in plain language. But no one can hand those SOPs to a bot because the current tools require brittle selectors and flows that cannot adapt. The result is a maintenance treadmill that limits growth.
Why RPA breaks here
Most RPA platforms rely on selectors, xpaths, or object IDs to locate elements on a screen. When the application updates a layout, these identifiers shift. A developer must find the new ID, update the bot, and redeploy. A 2023 industry survey of automation leaders found that 41 percent of bot downtime was caused by UI changes, and 28 percent was due to environment shifts such as Citrix upgrades or security patches. The cost of maintenance is measurable. By the time a bot is stable, the underlying application has often changed again. On virtual desktop infrastructure, RPA struggles because the environment is not a deterministic desktop image. The system state, window placement, and rendering can vary session to session. RPA bots assume a known desktop state, so they often fail before the first click. When an exception occurs, the typical RPA workflow halts and requires human intervention. The process does not recover on its own. This combination of brittle selectors, rebuild-on-change cycles, and halt-on-exception behavior creates a ceiling on how many workflows can be automated, especially on Citrix or virtualized environments.
What changes with computer use agents
- Survives UI changes: agents see the screen like a human and can identify buttons by their text and context, so they continue to work after a UI refresh or layout change.
- No brittle selectors: the agent uses the visual layout of the page rather than fixed IDs or xpaths, eliminating most rebuild-on-change work.
- Recovers from exceptions: when an unexpected state occurs, the agent can re-read the screen, adjust its plan, and continue instead of stopping.
- Follows SOPs as written: an SOP written in plain English can be fed directly to the agent, turning process documentation into an executable automation plan.
- Works on legacy and Citrix: because the agent controls the mouse and keyboard, it runs on any interface, including Citrix sessions, virtual desktops, and outdated applications that RPA cannot touch.
RPA works well for stable, high-volume, backend tasks. Computer use agents are the durable answer for changing UIs, exception-heavy workflows, and SOP-driven processes on Citrix and virtual desktops.
How to move without the risk
A phased approach lets you test computer use agents on the most painful workflows before committing to a broader rollout. Start by identifying a high-priority process that lives on a Citrix or virtual desktop, requires frequent human intervention, and has a clear SOP. Document the process in plain English, then use a computer use agent to pilot it. Measure the time reduction, error rate, and maintenance effort compared to the legacy RPA approach. If the pilot succeeds, expand to similar workflows and combine agents with RPA for hybrid environments. This approach lets you build confidence while keeping RPA in place for tasks where it already works well. Over time, you can expand agent use into more complex workflows and consolidate tools, but you do not need to rip and replace everything at once.
If your team is stuck on RPA because of Citrix and virtual desktop environments, there is a different path. Coasty computer use agents see the screen and follow SOPs directly, so they adapt to UI changes and recover from exceptions without constant rebuilding. Book a demo with the Coasty team to see how agents can handle your most stubborn workflows at https://cal.com/coasty/15min.
Want to see this in action?
View Case Studies