# September 2026

> September 2026 release notes for UiPath CLI.

## September 7, 2026

**UiPath CLI 1.201.0**

### Added

- **Unified evaluation commands on `uip or eval`** — `evaluator`, `eval-set`, `evaluation`, `run`, `schedule`, and `execute-and-evaluate`, covering runtime evaluations end to end. `execute-and-evaluate` is the former `run-offline-evals` renamed; the old name keeps working as an alias.
- **`uip insights alerts`** — read alert definitions with `list`, `get`, and `check-entitlement`.
- **`uip insights filter-folders` / `filter-processes` / `filter-queues` / `filter-machines`** — discover the folders, processes, queues, and machines that have recent activity, so a filtered Insights query can be scoped before it is run.
- **`uip maestro bpmn format` and `update-metadata`**, and `uip maestro registry pull`.
- **`uip rpa show-remote-connection`**.
- **`--feed-folder` on `uip rpa pack`, `uip rpa restore`, and `uip solution restore`** — resolve project dependencies from one Orchestrator folder's own library feed instead of searching every tenant feed. This replaces tenant-wide resolution rather than adding to it: a dependency published tenant-wide but absent from the named folder's feed is not found.
- **`--feed` on `uip solution publish`, `deploy run`, `deploy list`, and `packages list`** — publish to, deploy from, and filter by a specific feed. *Registers only on prerelease CLI builds.*
- **Integrated proxy authentication.** Set `UIPATH_PROXY_INTEGRATED_AUTH=true` to authenticate the proxy `CONNECT` tunnel with Windows Integrated Authentication — Kerberos/Negotiate or NTLM single sign-on, or an explicit account via `UIPATH_PROXY_USER`, `UIPATH_PROXY_PASSWORD`, and `UIPATH_PROXY_DOMAIN`. Without the opt-in the CLI behaves as before, supporting no-auth and Basic proxies.
- **New tools**: `uip ah` (Automation Hub), `uip tasks` (Action Center), and expanded `uip pm` (Process Mining) and `uip guardrails` surfaces. These do not yet have reference pages.
- **`uip ixp` folder deployments** — create, upgrade, and list Orchestrator folder deployments.

### Changed

- **`uip login status` reports who is logged in**, and the former single `Provider` field is split into three, so scripts reading `Provider` need updating.
- **`uip maestro bpmn refresh`** now also adds Integration Service connections.
- **Local filesystem permission failures are classified `local_permission_denied`** instead of a generic error, so a read-only directory is distinguishable from a server-side refusal.
- **`uip maestro flow` CEQL filters** follow general value-quoting and operator-alias rules.

### Deprecated

- **Project-wide `uip ixp` labellings `confirm` and `get-predictions`**.

### Fixed

This release includes bug fixes across the CLI host and the bundled tools. None of them change a documented behavior.

## September 2, 2026

**UiPath CLI 1.200.1**

A patch release. No commands, flags, or output shapes changed; the only user-visible change is to how the CLI decides which version of itself to run.

### Changed

- **`core.version` is now the whole CLI version policy.** The CLI no longer maps the authority you log into onto a version line. An exact pin freezes the version, a `MAJOR.MINOR` pin tracks that line, and leaving it unset follows the latest published version on the active channel.

  An unpinned CLI signed in to a non-production authority previously followed that environment's line, and now follows the latest published version. To hold a line, pin it explicitly:

  ```bash
  uip config set version 1.200
  ```

- **Unattended updates stop at the running major.** The daily update check will not install a new major on its own — a published `2.0.0` is not picked up unattended. An explicit `uip update` still crosses a major boundary.
- **Version resolution no longer makes a network call.** It is a plain config read, so `uip update` and `uip tools update` can no longer fail with *"Could not resolve your environment's version line"*, and `uip login` no longer clears the daily update marker.
- **`ResolvedBy: "environment"` is gone** from structured output, along with the environment-worded failure messages. Scripts that branch on that value need updating.

### Fixed

Bug fixes with no documented behavior change.