Generally available starting August 12, 2026 in Studio STS (S199+). Coming soon to Studio Web. A VS Code extension is also available in Public Preview.
TL;DR: Autopilot in Studio is a full coding agent. Not an upgrade — a rebuild: it plans, builds, runs, debugs, explains, and refactors automations alongside you. If you’re on Studio 2026.0.199 STS or later, you already have it. No new subscription, extra accounts, or API keys. Update, open the Autopilot panel and tell it what you need.
Building on our previous public preview announcement in June, we’re happy to let you know Autopilot as a coding agent in Studio is now GA - refined based on your feedback.
Built in, always available
Studio users spend most of their day in one place, so that’s where the coding agent should be. When we shipped the UiPath for Coding Agents skills and tools, we said Autopilot was getting rebuilt on the same foundation. This is that, now GA.
Autopilot loads UiPath’s official skills and uses the same CLI tooling we ship for external coding agents. What you get is an agent with full context on your project, native knowledge of UiPath conventions, and governance inside the UiPath trust boundary — no separate subscription, extra accounts, or context-switching.
If you tried Autopilot a while ago and formed an opinion, it’s worth trying again — it’s put on serious muscle since then.
What it does
Build from scratch — from idea to shipped automation
Autopilot now does real development work across the whole lifecycle, not just drafting. Things it handles today:
-
Plan from a spec — hand it a PDD or SDD and it plans, then builds
-
Build & edit — generates and modifies workflows and code that follow UiPath conventions
-
Run & troubleshoot — runs the automation and diagnoses failures
-
Debug & fix — finds the root cause and proposes the fix, including broken selectors
-
Extract from UIs — pulls data out of applications through UI automation, end to end from a prompt
-
Explain — walks you through an automation you’ve never seen before
-
Improve — restructures a workflow with better error handling and logging, hardens Object Repository selectors
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 that works
The part that makes RPA RPA — driving real applications through their interface — works on day one:
-
Build workflows using UI Automation from a prompt, with the latest UIA 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)
Coding agents don’t know what a selector is on their own — they learn it using the UiPath for Coding Agents skills and tools. With Autopilot, those come loaded by default, inside Studio.
Build from a prompt using Excel and UI Automation
It’s there after the build too
-
Troubleshoot a deployed job — “access denied” at 3am, and Autopilot points at the missing robot permission
-
Diagnose flaky runs — environment, data, or a real regression
-
Explain and document — inherit a five-year-old project and get it explained workflow by workflow
Same agent, same skills. The conventions that work for building work for everything after it.
Troubleshoot and fix a failing job
Explain a solution
What’s included
Autopilot is included with your Studio licence - Enterprise, Community, or trial; subject to a monthly usage quota. Worth knowing how the quota actually behaves:
-
The quota is per user licence, not pooled across your organisation.
-
How much you can get done within the quota varies with the model, the effort level and the complexity of what you ask. Run
/usagein Autopilot chat to see your own consumption; -
Autopilot actions like fix expression or generate commit message stay unlimited and don’t consume quota. The quota applies to Autopilot’s coding agent usage.
-
Admins can top up a specific user’s quota with Platform Units.
Licensing details: Unified Pricing licensing docs
Also GA: the Autopilot agent on Studio 25.10 LTS
If you’re on Studio 25.10 LTS, the Autopilot agent goes GA on August 12 too. It’s the earlier Autopilot capability set — it builds, edits and debugs RPA workflows proficiently. The coding agent capability set arrives with Studio 26.10 LTS.
Where is Autopilot coming next?
-
VS Code — Autopilot is also available as an extension in Public Preview.
-
Studio Web — availability coming soon.
-
LTS — this capability set arrives in Studio 26.10 LTS.
Try it out
Update to the latest Studio STS, open the Autopilot panel in a project, and give it something real — build from a spec, hand it a broken selector, or ask it to explain that inherited project nobody wants to touch.
-–
Last, but not least: thank you! 
The preview feedback shaped what shipped — what we prioritised, what we fixed, and what we chose to postpone.
Keep it coming: run /uipath-feedback directly in Autopilot. It’s the fastest route to us: it creates a report with diagnostics, what happened, and the context around it without you having to describe it. You’ll just approve the report before sending.