- Getting started
- Capabilities
- Data privacy and governance
- Product availability
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- Autopilot usage pool for testing
- Best practices and limitations
- Supported models and limits
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Find obsolete tests
- Generate tests for SAP transactions
- Generate synthetic test data
- Generate test reports
- Generate coded test cases
- Search Test Manager project
- Troubleshooting
- Autopilot for Everyone
- About Autopilot for Everyone
- Licensing
- User types
- Data sources
- Toolset automations
- Localization
- Prerequisites
- Autopilot widget
- The Autopilot for Everyone tenant card
- Prerequisites for installation
- Enabling Anthropic models
- Installing Autopilot for Everyone
- Updating Autopilot for Everyone
- Uninstalling Autopilot for Everyone
- Configuring Autopilot for Everyone
- Disabling the Autopilot welcome screen in Assistant
- Configuring an LLM for Autopilot for Everyone
- Deploying toolset automations
- Prompt-to-response flow
- Launching Autopilot for Everyone
- Autopilot settings for business users
- Using a specialized Autopilot
- Using a starting prompt
- Uploading and analyzing files
- Running automations
- Interacting with Autopilot answers
- Using suggested prompts
- Starting a new chat
- Chat history
- Providing general feedback
- Clipboard AI Enterprise version
- Designing relevant automations for Autopilot for Everyone
- Troubleshooting
Autopilot as a coding agent for RPA workflow projects in Studio Web: what you can do today and the tools it uses.
Autopilot in Studio Web can read, explain, and review RPA workflow files using natural language, but does not author them. This is a smaller set of capabilities than the coding agent in Studio Desktop, which remains the complete RPA experience.
Use Autopilot to:
- Understand what an existing workflow (
.xamlor.cs) or test case does. - Review a workflow against known RPA issues, such as long-running workflow patterns and common Studio pitfalls.
- Troubleshoot a workflow and describe the exact fix — file, activity, property, or expression — for you to apply in the Studio Web designer.
- Create a new, empty RPA project scaffold.
- Run an existing project.
Tools
Before reviewing a project, Autopilot reads the RPA skill's Studio Web scope, plus the test skill. In this host, it does not create, edit, rename, or delete any file in an RPA project. There is no validate or build step to check a workflow against, so authoring is not supported here.
It can run uip rpa init to scaffold a new project and uip rpa run to run an existing one. These are the only two rpa UiPath CLI (uip) verbs available in Studio Web, both served directly by the Studio Web host rather than the browser CLI bundle. It also uses the platform skill for connections, connector activities, assets, queues, and jobs. It can read and search project files, but not edit them.
Known limitations
- No authoring in Studio Web — Autopilot does not create, edit, rename, or delete RPA project files here. It can read, review, and troubleshoot them, and describe the fix for you to apply in the designer. Scaffolding a new project (
uip rpa init) and running an existing one (uip rpa run) are the only CLI actions available. - For the complete RPA experience — build, edit, validate, run, debug, and publish — use Autopilot in Studio Desktop.
- Support for RPA workflows in Studio Web is experimental: review its findings before you act on them. You can switch back to the classic Autopilot experience from the chat title bar at any time — for RPA workflows in Studio Web, the classic experience provides the generic set of tools only (web search and documentation search, no project-specific tools).