# Executing UiPath CLI tasks

> This section explains how to execute tasks using the UiPath Command Line Interface (CLI), which is available in multiple platform-specific variants:

This section explains how to execute tasks using the UiPath Command Line Interface (CLI), which is available in multiple platform-specific variants:

- **UiPath.CLI.Windows** – for Windows environments
- **UiPath.CLI.Linux** – for Linux environments
- **UiPath.CLI.macOS** – for macOS environments
- **UiPath.CLI.Windows.Legacy** – for standalone RPA Windows - Legacy projects only

Most tasks use the same syntax across platforms, with minor differences in how the CLI is invoked (e.g., `uipcli.exe` vs `dotnet uipcli.dll`).

To learn more about supported CLI tasks, see:

- [Packing projects into a package](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/packing-projects-into-a-package)
- [Analyzing a project](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/analyzing-a-project)
- [Deploying a package to Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/deploying-a-package-to-orchestrator)
- [Running a job inside Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/running-a-job-inside-orchestrator)
- [Testing a package or running a test set](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/testing-a-packagerunning-a-test-set)
- [Testing multiple packages](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/testing-multiple-packages)
- [Deploying assets to Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/deploying-assets-to-orchestrator)
- [Deleting assets from Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/deleting-assets-from-orchestrator)
- [Running tasks using JSON configuration](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/running-tasks-using-json-configuration)
- [Restoring automation dependencies](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/restoring-automation-dependencies)

For Solution-related tasks introduced in 25.10, refer to [Working with Solutions](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/working-with-solutions).

## API access application scopes (standalone Projects)

The table below lists the Test Manager and Orchestrator scopes required by CLI tasks related to standalone projects. These scopes are needed for the UiPath CLI – Test Manager integration. 

| Application Scope       | Description                                      |
|-------------------------|--------------------------------------------------|
| **OR.Assets**           | Read/write access to assets                      |
| **OR.BackgroundTasks**  | Read/write access to background tasks            |
| **OR.Execution**        | Read/write access to execution data              |
| **OR.Folders**          | Read/write access to folders                     |
| **OR.Jobs**             | Read/write access to jobs                        |
| **OR.Machines.Read**    | Read-only access to machines                     |
| **OR.Monitoring**       | Read/write access to monitoring data             |
| **OR.Robots.Read**      | Read-only access to robots                       |
| **OR.Settings.Read**    | Read-only access to settings                     |
| **TM.Projects**         | Projects read and write access in Test Manager   |
| **TM.TestSets**         | TestSets read and write access in Test Manager   |
| **TM.TestExecutions**   | TestExecutions read and write access in Test Manager |

In addition to the task-specific scopes, **OR.Default** can be used as a wildcard scope. It provides flexible access control at organization and folder levels, suitable for most CLI-based automations. See [Declaring scopes](https://docs.uipath.com/automation-cloud/automation-cloud/latest/api-guide/accessing-uipath-resources-using-external-applications#declaring-scopes) for details.

:::note
For **Solutions**, the required scopes differ and are described separately in [Authentication and scopes for Solutions](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/solutions-authentication-and-scopes).
:::

## Registering an external application

To authenticate the CLI with Orchestrator, you must register an external application in Automation Cloud.

See: [Managing external OAuth applications](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/managing-external-applications#adding-an-external-application)

:::note
If you're running `uipcli` on the same machine where Studio is open, make sure to close the project in Studio to avoid locking errors.
:::