- 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 BPMN projects in Studio Web: what you can do and the tools it uses.
Autopilot in Studio Web generates and edits Maestro BPMN process models using natural language — the same coding agent that ships with Studio Desktop, adapted to the BPMN project type.
Use Autopilot to:
- Generate a BPMN process from a plain-language description or from an image of a process — a sketch, a whiteboard photo, or a screenshot of another diagram.
- Edit an existing diagram's structure — gateways, events, boundary events, subprocesses, call activities, multi-instance loops, sequence-flow conditions, and variables — while preserving elements it did not author.
- Add an extension node — an RPA job, an agent, a human-in-the-loop step, a queue, a business rule, an API workflow, an Integration Service connector, an internal message, or a timer.
- Apply a known process pattern, such as an approval chain, smart triage, a high-volume batch, or failure escalation, adapted to the process at hand.
- Validate the diagram against the canvas rules before import.
- Package, upload, publish, or run a project, and manage its jobs and instances.
- Diagnose a failed or misbehaving run, tracing an incident back to the BPMN element that caused it.
Tools
Before making changes, Autopilot reads the Maestro BPMN skill for the open project. Node payloads for registered types come from the UiPath registry rather than being hand-authored. The surrounding process structure — scaffold, sequence flows, gateways, and diagram layout — is authored from the BPMN spec and canvas contract.
Autopilot uses the human-in-the-loop skill to wire in approval steps. It uses the maestro UiPath CLI (uip) command group to validate, package, publish, run, and diagnose the project.
Any cloud-side action — upload, publish, deploy, run, pause, resume, cancel, retry, or migrate — requires your confirmation, and local validation must pass first. Diagnosing a run reads incidents, variables, and element executions from the deployed asset through the CLI.
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 BPMN projects at the solution level.
Known limitations
Support for Maestro BPMN in Studio Web is experimental: review generated diagrams and expressions before you run or publish them. You can switch back to the classic Autopilot agent experience for Maestro BPMN from the chat title bar at any time.