AI agents replace UiPath only when the model runs at authoring time, not at runtime.

In specific workflow categories, yes. The replacements that survive enterprise audit and reliability share one architectural choice: the model runs at authoring time, not at runtime. A human records the workflow once, the model converts the recording into a deterministic workflow file, and the runtime replays the file with no model in the loop. Pure agentic systems that call an LLM at every UI step have not held up at scale. UiPath itself has split its product line along the same boundary: classic RPA Robot for execution, AI Center and Agent Builder for the bolted-on cognitive layer. The category name is moving from RPA to agentic automation, but the production architecture is still hybrid.

Three reasons. First, latency: an LLM call per UI action stacks into 30 to 60 seconds of wall time per step, which is fine in a demo and unacceptable on a queue of 5,000 invoices. Second, audit: a compliance officer cannot sign off on a workflow whose action sequence is decided by a model on every run because the action set is non-deterministic by definition. Third, regression: a model upgrade silently changes which buttons get clicked, and you find out three days later when reconciliation breaks. The hybrid version (model at authoring, code at runtime) keeps the model where its strengths matter (understanding intent from a recording) and out of the place where determinism matters (replay).

Ask one question: what is the exact artifact your runtime reads, and what programs interpret it. If the answer is 'a prompt and a screenshot', the model is in the runtime. If the answer is 'a code file in git that we generated once and now replay', the model is at authoring. Mediar's runtime artifact is a TypeScript file. The executor that reads it is a 871-line Rust crate at crates/executor/src/services/typescript_executor.rs in the open-source repo at github.com/mediar-ai/terminator. You can grep that file for gemini, claude, openai, or anthropic and find zero matches. That single check disambiguates the architecture.

UiPath Agent Builder is an addition to the existing platform, not a replacement. The base UiPath Robot still runs the same selector-based architecture it has run since 2014; Agent Builder bolts agentic capabilities on top via the existing Robot runtime. UiPath has been clear in its own communications, including the 2024 Forward conference and recent diginomica coverage, that the strategy is hybrid: keep deterministic RPA for the workflows that need it, layer agents on top for the parts that need cognition. The marketing pivot to agentic automation is real; the engineering pivot is gradual. Buyers should treat 'replacing UiPath RPA with an AI agent' the same way: the workflows that move are the ones where a deterministic replay is enough, paired with a smarter authoring layer.

Concretely: a developer or analyst opens the Mediar desktop app, hits record, and walks the workflow once on the same machine that normally runs it. The recorder captures six event types defined in apps/desktop/src-tauri/src/recording_processor.rs at line 250: button_click, browser_click, text_input_completed, browser_tab_navigation, application_switch, file_opened. Those events plus snapshot accessibility trees go to the authoring pipeline, which emits a TypeScript file. The file is checked into git and queued. From then on the executor pulls it off the queue, calls MCP execute_sequence, and the Terminator SDK drives Windows UI Automation, the same accessibility surface a screen reader uses. Re-recording for a new workflow takes hours, not the weeks of selector authoring a comparable UiPath rollout would take.

A UiPath Robot resolves a recorded XPath-style selector at replay; a UI change that breaks the selector throws and the workflow fails. Mediar's executor walks four match strategies in apps/desktop/src-tauri/src/focus_state.rs lines 168 to 196: automation or accessibility id, then window plus bounds, then visible text, then parent window focus. Most enterprise UI patches (a label rename, a panel reorder, a control id change) are absorbed by one of the first three. The point is not magic recovery. It is that a single selector miss does not fail the run, which compounds at any organization with more than a handful of workflows touching the same UI estate.

UiPath public list pricing starts around $420 per month per attended Robot, plus per-Studio-seat developer fees and per-tier Orchestrator licensing. Enterprise contracts at the RPA Center of Excellence level commonly land in the $100K to $500K-plus range for the first year, with annual renewals. Mediar charges $0.75 per minute of executor runtime, plus a $10K turn-key program fee that converts to credits. A workflow that runs 10 minutes a day costs roughly $1,575 a year in runtime. The comparison the marketing site cites (around 20% of UiPath cost) is at typical small-to-mid enterprise volumes; savings shrink at very high concurrency and grow on long-tail workflows.

Yes. The honest path is parallel. Keep UiPath running for stable workflows that have not changed in months and pay for themselves at current selector maintenance costs. Route new automation requests, especially the ones stalled for selector breakage, to the AI-agent authoring path. Compare in production over a quarter on three numbers: time from request to first run, count of failed runs per 1,000 invocations, and developer hours per workflow per month. Whichever architecture wins the third number wins the long term, because it is the only one that compounds.

Two places. First, browser-only flows on modern SaaS where a stable API exists. If the data lives behind an OpenAPI spec, an API-first integration beats both UiPath and a desktop AI agent on cost and reliability. Second, workflows that need true free-form planning that cannot be captured by recording (multi-day case investigations, fraud triage, novel exception handling). For those, agentic systems with the model at runtime are still the right answer. The boundary is recording-shaped repetitive work on legacy desktop systems with no API, which is where UiPath rolled out in the first place and where the selector-vs-accessibility tradeoff actually matters.