UiPath CLI user guide

UiPath CLI 1.x (uip, distributed on npm as @uipath/cli) replaces the legacy .NET CLI (uipcli.exe, distributed as UiPath.CLI through calendar releases 2023.10, 2024.10, and 2025.10). This page explains who should migrate, what changes at the tooling level, and how to navigate the four detail pages below.

If you only want the flag-for-flag answer to "what do I type instead of uipcli <verb>?", jump to Command map and Flag renames.

You should migrate if any of the following apply:

You can stay on the legacy CLI for now if you need a Windows-only feature that has not yet been ported to the cross-platform uip rpa tool (Studio debugger integration, validate, find-package, find-activities, type-definition). A sibling uip rpa-legacy tool wraps the 2025.10 binary on Windows; see uip rpa — Windows-only legacy wrapper. Everything else — packaging on Linux/macOS, Orchestrator operations, Solutions, Test Manager, Agents, Flows, Maestro — is in uip today.

See What's new for the rewrite summary.

Run uipcli --version (or dotnet uipcli.dll --version). The output looks like 23.10.8817.35919, 24.10.9248.xxxxx, or 25.10.xxxx.xxxxx. The migration paths below cover all three.

These three appear in nearly every migration. See Breaking changes for the full list.

Complete these four steps before you start porting a pipeline.

Commit a known-good copy of every azure-pipelines.yml, Jenkinsfile, .github/workflows/*.yml, or .gitlab-ci.yml on a branch (or tag). The port is easier to review as a diff.

Always install with an explicit version during migration so pipeline behavior does not change unexpectedly:

Tools pin implicitly to the CLI's MAJOR.MINOR line (see Versioning), so a pinned CLI also pins every tool to a known minor range. For strict patch-level reproducibility, pin tools too — see the "Pinning versions in CI" section of Scripting patterns.

Cross-reference flag behavior during the port. The 2025.10 reference lives at docs.uipath.com — UiPath Command Line Interface (2025.10). Keep it open in a tab.

The legacy CLI accepted several authentication modes; the new CLI collapses CI authentication to External Application client credentials. Create the app now so the port has something to point at. See Authentication — Flow 2.

Each page below is focused enough to review in one sitting. Work through them in order if you're porting a full pipeline; jump straight to the one you need if you only want a specific answer.

Every legacy verb — package pack, package analyze, package deploy, package restore, job run, test run, test parallel, asset deploy, asset delete, solution pack, solution deploy, run — with its uip equivalent, a 1:1 / multi-step / removed classification, and a before/after shell snippet for every non-trivial row.

Flag-level mapping with the auth block at the top. Legacy -u/-p/-t/-a/-A/-I/-S/-o/--applicationScope/--identityUrl/--outputType/--traceLevel mapped to their uip counterparts (or called out as removed, with the replacement). Read this alongside the Command map — the Command map shows the verb, Flag renames shows the flag.

Prose coverage of the changes that break pipelines without warning. Auth mode removals, env-var auto-reading removal, exit-code contract tightening, JSON-stdout default, calendar-versioned NuGet folders gone, .NET runtime dropped. One paragraph per change with a "what to do" remediation.

Before/after snippets for Azure DevOps and Jenkins (required), with shorter GitHub Actions and GitLab CI snippets. Cross-linked to the full CI/CD recipes for complete pipelines.