Public preview. Available now in Studio Desktop STS (S195 and later - including the current S197), coming soon in Web. We want to share it early because the preview is exactly when your feedback shapes what ships.
TLDR: Autopilot in Studio Desktop is now a full coding agent - it plans, builds, runs, debugs, explains, and refactors automations alongside you. If you’re on Studio STS S195 or later, you already have it. No new subscriptions, no extra accounts. Update, open the Autopilot panel, and tell it what you need.
Why
Studio users spend most of their time in one place - so that’s where the coding agent should live too. When we shipped coding agents for third-party tools, we said Autopilot was getting a massive upgrade built on the same skills and tooling. This is it. Autopilot now loads UiPath’s official skills and uses the same CLI tooling we ship for third-party coding agents. The result is an agent with full context on your project, native knowledge of UiPath conventions, and governance built in - no separate subscription, no extra accounts, no context-switching.
Already tried Autopilot? Try it again - it can now do much more than generating workflows: it plans, builds, runs, debugs, and fixes alongside you.
How
If you’re on Studio STS (S195) or higher, you’re good to go - that’s the only prerequisite. No separate tool to install, no agent to wire up. It auto-loads the UiPath skills and connects that same tooling to your project, Studio, and Orchestrator.
Build from scratch - from idea to shipped automation
What you can do
Autopilot now does real development work across the whole lifecycle, not just drafting. Things it handles today:
-
Plan from a spec - feed it a PDD or a requirement, then watch it plan and build the automation
-
Build & edit - generate and modify workflows and code that adhere to UiPath conventions
-
Run & troubleshoot - run the automation and help diagnose failures
-
Debug & fix - find the issue and propose the fix. Including broken selectors - point it at a failing Click and it names the root cause and repairs it (try it on the RPA Challenge)
-
Extract from UIs - pull data from applications through UI automation, end-to-end from a prompt with the latest UIA package
-
Explain - walk you through an existing automation you’ve never seen
-
Improve - restructure a workflow with better error handling and logging, or harden Object Repository selectors
-
And many more. If you can describe it, Autopilot can probably do it.
A few examples of what you can build by prompt:
-
Filter every invoice row above 1,000 into a new sheet → a working Excel automation in minutes, no manual activity-wiring
-
Build the onboarding process from this SDD → feed it a 30-page spec and get a full automation back, UI steps and all
-
Scrape this site into a table → a live website turned into a clean DataTable from a single prompt
-
Turn these PDF invoices into a CSV and send it to finance → extraction → transformation → delivery, wired end-to-end
-
Split this 80-activity workflow into smaller, reusable pieces → modular sub-workflows under 20 activities each, properly invoked - no more scrolling through one giant sequence
Edit, fix, and debug an existing workflow
UI Automation works too
The thing that makes RPA RPA - driving real applications through their UI - works on day one:
-
Build workflows leveraging UI Automation from a prompt with the latest UI Automation package.
-
Extract data from application UIs into structured tables.
-
Fix broken selectors - point it at a failing Click, and it names the root cause and repairs it (try it on the RPA Challenge)
This is the part general-purpose coding agents struggle with - they don’t know what a selector is. Autopilot does, because it’s running on the same UiPath skills, inside Studio, with the Object Repository right there.
Build from a prompt using Excel and UI Automation
More than building
Building is the headline, but the same agent handles what comes after a job is deployed:
-
Troubleshoot a failing deployed job - “access denied” at 3 am → Autopilot diagnoses the missing robot permissions and points you at the fix.
-
Diagnose flaky runs - is it the environment, the data, or a real regression?
-
Explain & document - inherit a 5-year-old project and have its workflow explained, workflow by workflow.
Same Autopilot. Same skills. The conventions that work for building work for everything after it, too.
Troubleshoot and fix a failing job
Explain a solution
Why Autopilot
-
Included - no separate subscription, no token bill, within a monthly usage limit
-
No extra accounts - no third-party sign-up, no API keys to manage; it’s all UiPath, already pointed at your project
-
Native governance - everything runs inside the UiPath trust boundary, with destructive actions gated, admin-capped autonomy, and audit logging
-
Studio stays the visual layer - every change Autopilot makes is something you can open, inspect, debug, and govern, exactly as before
If your team prefers a different IDE or a third-party coding agent, that’s great. But if you live in Studio and want the least hassle with maximum control, Autopilot is the fastest path from idea to shipped automation.
Try it
Update to the latest Studio STS, open the Autopilot panel in a project, and throw something real at it - build an automation from a spec, hand it a broken selector, or ask it to explain that inherited project nobody wants to touch.
If it worked: reply in this thread with what you asked and what Autopilot did - it tells us what to double down on for GA.
If something’s off: tell us in the thread too - include your prompt, what you expected, and what happened instead. This is exactly what a public preview is for: your feedback shapes what ships.
