- 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
- 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 agent
Documentation for the Autopilot agent experience, a multi-step conversational interface available in Studio Desktop and Test Manager.
Autopilot agent is the multi-step conversational experience that lets you interact with Autopilot through a chat interface inside UiPath products. Unlike Autopilot actions, which are single-trigger operations, the agent maintains context across a conversation and can perform work one step at a time with you driving each step.
Autopilot agent is available in Studio Desktop (2025.10.8+), Studio Web, and Test Manager. In Studio Desktop, it has been succeeded by the full coding agent experience starting with STS 2026.0.199+, but the agent remains supported. In Studio Web, the coding agent is now in Public Preview across all project types; you can switch back to Autopilot agent from the chat title bar at any time. Refer to Product availability for the full list of products and capabilities.
How it works
The Autopilot chat interface provides a conversational panel where you can:
- Ask questions about your project, automations, or UiPath documentation
- Request workflow generation, editing, or explanations
- Iteratively refine results through follow-up prompts
- Get contextual suggestions based on the product and page you are working in
Each product where Autopilot agent is available has its own set of connected sources (tools) that determine what Autopilot can access and do.
Here are the main capabilities of the chat experience:
- Context retention—remembers previous inputs and decisions.
- Prompt refinement—lets you edit your prompt in real-time to improve outcomes without starting from scratch.
- Conversational experience—uses natural language to ask questions and make changes.
- Inline suggestions—offers recommendations directly in the chat, specific to your current context.
- Unified workspace—keeps all interactions, iterations, and results in one place.
- Workflow continuity—maintains the flow across steps and stages.
- Interactive debugging—helps you identify and fix issues by asking follow-up questions or clarifying intent.
- Code and logic awareness—understands the structure of your automation or code and provides relevant guidance.
Interaction modes
In the user interface, the Edit dropdown in the chat input area allows you to switch between two interaction modes:
- Edit — Requires user confirmation to perform change actions.
- Agent — (Experimental) Performs actions automatically without requiring user confirmation.
Available models
For the list of supported models and how model routing works for Autopilot, see AI features and model routing.
- To use the available LLMs, make sure you have the required policies in AI Trust Layer.
- Specifically for the documentation AI functionality, Autopilot uses Azure OpenAI.
Kimi K2.6 support in Automation Suite
In Automation Suite, the Kimi K2.6 model still appears under its interim display name, Virtuoso. Everywhere else, Autopilot displays the model under its actual name, Kimi K2.6.
No action is needed on your side. Starting with the 2026.10 releases, Automation Suite will also display the model under its actual name.
The AI Trust Layer policy
To use the AI capabilities provided by Autopilot, make sure you have an AI Trust Layer policy active and deployed to your tenant.
Learn how to:
- Create a policy
- Configure the policy for AI Trust Layer
- Deploy the policy to the tenant where you want use Autopilot
Disclaimer about Autopilot responses
Autopilot is designed to assist you across different UiPath products, and provides AI-powered support for a variety of tasks, such as building and editing automations, understanding complex workflows, or retrieving relevant information from documentation or other sources. While it can be highly effective, it may occasionally generate responses that are inaccurate, misleading, or incomplete. This is a known limitation of large language models and is sometimes referred to as "hallucination."
For example:
- Autopilot may suggest steps that do not apply to your current workflow.
- It may provide explanations that sound correct but are factually incorrect or based on outdated logic.
- When working with external information, such as documentation or web search, it may overlook important details or misinterpret source content.
Always review and validate its responses, especially when dealing with production workflows, data handling, or error-prone logic:
- Double-check suggestions before applying them, particularly in critical or high-risk workflows.
- Use the thumbs down button in the chat interface to flag unhelpful or incorrect responses.
- Review documentation links or search citations if provided. These often contain additional context not included in the summary.
Autopilot is a powerful assistant which works best as a collaborator, not a decision-maker. Your input and judgment remain essential for building safe, accurate, and effective automations.