- 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 Maestro Case projects in Studio Web: what you can do and the tools it uses.
Autopilot in Studio Web drafts and edits Maestro Case projects using natural language — the same coding agent that ships with Studio Desktop, adapted to the Case Management project type.
Use Autopilot to:
- Design a case from a plain-language description — presenting the case snapshot, primary journey, other paths, SLA responses, business rules, and resources for your review before it builds anything.
- Build a case from an approved design or an existing spec — stages, tasks, triggers, conditions, SLAs and escalations, and variables.
- Add approval gates, escalations, write-back validation, or data-enrichment checkpoints to a case.
- Make a targeted edit to an existing case — a stage, task, condition, or trigger.
- Validate a case against its design and fix errors before you run or publish it.
Tools
Before making changes, Autopilot reads the Maestro Case skill for the open project. If no design exists yet, it hands off to the planner skill to produce one with you first, before building starts. That design covers the case snapshot, primary journey, SLA responses, business rules, and resources.
Once a design exists, Autopilot uses the human-in-the-loop skill to wire in approval gates and escalations. It uses the case and maestro UiPath CLI (uip) command groups for resource discovery, validation, debugging, and publishing.
Debugging a case runs real emails, messages, and API calls. Publishing to Studio Web or Orchestrator ships to your tenant. Autopilot asks for your confirmation before either.
It also uses the platform skill for connections, connector activities, assets, queues, and jobs. It can read, edit, and search project files, and create new Case projects at the solution level.
Known limitations
Support for Maestro Case in Studio Web is experimental: review generated case plans before you run or publish them. You can switch back to the classic Autopilot experience from the chat title bar at any time — for Case projects, the classic experience provides the generic set of tools only (web search and documentation search, no project-specific tools).