autopilot
latest
false
Autopilot user guide
- 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 Function projects in Studio Web: what you can do today and the tools it uses.
Autopilot in Studio Web can read and edit Function source files using natural language.
Use Autopilot to:
- Understand what an existing function does — its input/output contract and whether it runs as an HTTP endpoint or a job.
- Edit Python or TypeScript/JavaScript source files — handlers, typed input/output schemas, and error handling.
- Explain how a function calls UiPath platform APIs, through the Python SDK or the
ctx.userandctx.robottokens in TypeScript/JavaScript. - Spot contract or configuration issues — a stale schema, an extensionless import, or a runtime dependency declared in the wrong place.
Tools
Before making changes, Autopilot reads the Functions skill for the open project. This skill covers both Python and TypeScript/JavaScript functions: typed input/output contracts, the functions map in uipath.json that identifies the project, and the platform APIs a function can call through the SDK.
It can read, edit, and search project files, and create new Function projects at the solution level. It also uses the platform skill for connections, connector activities, assets, queues, and jobs.
Known limitations
- CLI not yet available in Studio Web — the
functionUiPath CLI (uip) command group is not yet shipped to Studio Web, so Autopilot cannot write, run, or publish functions from the browser today. It can only read and edit files. - Support for Functions in Studio Web is experimental: review generated changes before you run or publish them. You can switch back to the classic Autopilot experience from the chat title bar at any time — for Functions, the classic experience provides the generic set of tools only (web search and documentation search, no project-specific tools).