- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- Packing projects into a package
- Analyzing a project
- Deploying a package to Orchestrator
- Running a job inside Orchestrator
- Testing a package or running a test set
- Testing multiple packages
- Deploying assets to Orchestrator
- Deleting assets from Orchestrator
- Running tasks using JSON configuration
- Restoring automation dependencies
- Troubleshooting UiPath CLI
- Azure DevOps extension
- Jenkins plugin
CI/CD integrations user guide
About UiPath CLI
UiPath® provides a command-line interface (CLI) that enables you to execute automation lifecycle tasks such as packaging, deploying, testing, and running automations in Orchestrator. The CLI is designed for integration with third-party tools like GitLab, Jenkins, or Azure DevOps, allowing automation teams to adopt CI/CD best practices at scale.
UiPath CLI can be used with Orchestrator deployed via Automation Cloud™, Automation Suite, or Standalone.
Common use cases
UiPath CLI is built to enable Automation Lifecycle Management (ALM) through seamless integration with CI/CD pipelines.
It allows automation teams to:
- Package and version RPA projects (Cross-platform, Windows, Windows - Legacy) into portable NuGet artifacts.
- Deploy and promote projects across environments using repeatable, auditable pipelines.
- Integrate with external tools like Azure DevOps, GitLab, or Jenkins for continuous integration and deployment.
- Package, deploy, and activate multi-project Solutions — combining RPA, Agentic workflows, API processes, and configuration into a single, versioned unit.
This enables enterprise-grade automation delivery at scale, fully aligned with DevOps practices.
Solutions support
UiPath CLI supports Solutions — a packaging format that combines multiple project types and configurations into a single deployable unit.
Solutions can include:
- Cross-platform or Windows RPA projects (Windows - Legacy projects are not supported within Solutions).
- Agents, Agentic processes, and API Workflows.
- Environment configuration and binding files.
This simplifies how enterprise teams manage full-stack automation and apply DevOps discipline across environments and tenants.
Learn more in Working with Solutions.
CLI packages
UiPath CLI is distributed in the following packages:
| Package Name | Supported OS | Supported Project Types |
|---|---|---|
UiPath.CLI.Windows | Windows | RPA Projects (Cross-platform/Windows), Solutions |
UiPath.CLI.Linux | Linux | RPA Projects (Cross-platform), Solutions |
UiPath.CLI.Windows.Legacy | Windows | RPA Projects (Windows - Legacy) 1 |
1 Use UiPath.CLI.Windows.Legacy only for standalone Windows - Legacy projects that are not part of a Solution.
Runtime requirements
All UiPath CLI packages (Windows, Linux, and Legacy) require .NET 8.
- On Windows, install the .NET Desktop Runtime 8 (included with the .NET SDK).
- On Linux, ensure the .NET Runtime 8 is available in your environment.
- The CLI is compatible with UiPath Robot 2025.10 and newer.
Unless otherwise specified, all 25.x CLI versions are compatible with Robot 2025.10 and later.
Integration with CI/CD plugins (Azure DevOps and Jenkins)
Starting with version 25.10, UiPath CLI is distributed together with major updates of the Azure DevOps and Jenkins plugins.
- The plugin versions install UiPath CLI 25.10 (and later) in one of the following flavors:
UiPath.CLI.WindowsUiPath.CLI.LinuxUiPath.CLI.Windows.Legacy
- Older CLI versions (23.x / 24.x) are not installed automatically by the updated plugins.
When upgrading the Azure DevOps or Jenkins plugins, review your pipeline definitions and ensure they reference the correct CLI flavor. Existing pipelines that reference older CLI versions must be updated to use one of the new CLI package names.
Limitations
- UiPath CLI does not support SSO authentication.
- Projects using Local Triggers cannot be built using CLI.
- Package signing for standalone projects: UiPath CLI lacks the functionality to sign a package, a feature that is available when you publish the package from Studio. In this case, the only option is to sign the package after it is built using UiPath CLI. For details, refer to the sign command. This signing option works also for Azure DevOps and Jenkins.
