autopilot
latest
false
Autopilot user guide
- Getting started
- Capabilities
- Data privacy and governance
- Product availability
- Studio Desktop STS
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- 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 in Studio Desktop STS: what you can do and the tools it uses.
Autopilot in Studio Desktop STS is an agentic AI assistant that plans, executes, and validates multi-step automation development tasks using natural language, operating through a discover, reason, execute, validate, and fix cycle backed by the UiPath CLI runtime.
Note:
Autopilot requires UiPath CLI, which is installed automatically. For details, refer to the UiPath CLI documentation.
Use Autopilot to:
- Create new RPA workflows (.xaml) from a plain-language description.
- Edit existing workflows — add, remove, replace, or restructure activities.
- Generate C# coded workflows, coded test cases, and utility source files.
- Configure activity properties, variables, arguments, and control flow.
- Understand, explain, or summarize what existing activities and code blocks do.
- Improve workflow logic with better structure and error handling.
- Debug, run, and validate workflows directly from the chat.
- Find and install NuGet packages required by generated workflows.
- Discover available UiPath activities and retrieve their default XAML templates.
- Analyze files for linting errors and apply auto-fixes.
- Automate manual test cases retrieved from Test Manager.
- Load and analyze Healing Agent intervention data from robot execution jobs.
- Search documentation and the web for UiPath best practices.
- Ask for clarification interactively mid-task.
- Assign isolated tasks to specialized subagents.
- Call tools on connected MCP servers for external service integrations.
Tools
Autopilot leverages a range of tools to support your automation work. By default, all tools are enabled. Autopilot can:
- Understand, create, edit, debug, publish, and deploy automations.
- Install and update dependencies.
- Fix errors.
- Create and manage test cases.
- Troubleshoot production errors.
- Run PowerShell commands or search the web.
- Make a plan, spin up subagents, and maintain persistent memory for your specific user account.
For more about tools, skills, and how Autopilot generates workflows, refer to RPA workflows. For platform operations and diagnostics, refer to Operate and Troubleshoot.
Known limitations
- UiPath CLI is required and is installed automatically with Studio.
- Web Search requires access to Gemini models. You do not need to select a Gemini model as your active model, but your user or organization must have access to one.
- Voice to chat (Whisper) requires access to OpenAI models. You do not need to select an OpenAI model as your active model, but your user or organization must have access to one.
- AI model display name — Kimi K2.6 appears as "Helix" in Studio STS 2026.0.x. It will display its real name starting 2026.10.
- Legacy Autopilot panel deprecation — The embedded "Fix validation error" and "UiPath documentation search" actions, and the legacy Autopilot panel (Fix error, doc search, Healing Agent) are scheduled for removal in Studio 2026.10. Error-fixing and doc search will continue through the Autopilot coding agent; Healing Agent will move to its own dedicated panel.
- MCP Tool only calls tools on MCP servers that are already configured and connected in the Studio environment.
- Proxy Tool only accesses tools that Studio Desktop has explicitly registered as host tools.