- 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 Coded App projects in Studio Web: what you can do today and the tools it uses.
Autopilot in Studio Web can read and edit Coded App source files using natural language.
A Coded App is a project type in Studio Web, distinct from a coded agent. For agent projects, refer to Agent.
Use Autopilot to:
- Understand the structure of an existing Coded Web App or Coded Action App.
- Edit React or TypeScript source files — components, SDK calls, and configuration.
- Explain how a component uses the
@uipath/uipath-typescriptSDK to reach Orchestrator, Data Fabric, Maestro, Action Center, or Conversational Agent data. - Edit the action schema (
action-schema.json) that defines a Coded Action App's inputs, outputs, and outcomes. - Spot configuration issues — OAuth scopes in
uipath.json, base URL, or asset paths that are not relative.
Tools
Before making changes, Autopilot reads the Coded Apps skill for the open project. This skill distinguishes Coded Web Apps (custom frontends deployed to Automation Cloud) from Coded Action Apps (forms rendered inside Action Center human tasks). It also documents the @uipath/uipath-typescript SDK's Orchestrator, Data Fabric, Maestro, Action Center, and Conversational Agent modules.
It can read, edit, and search project files, and create new Coded App 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
codedappUiPath CLI (uip) command group is not yet shipped to Studio Web, so Autopilot cannot scaffold, pack, publish, or deploy Coded Apps from the browser today. It can only read and edit files. - Support for Coded Apps 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 Coded Apps, the classic experience provides the generic set of tools only (web search and documentation search, no project-specific tools).