Global options accepted by every `uip` invocation, covering output format, output filter, log level, and log file.

Every uip invocation is pre-scanned for a fixed set of global options before any tool or subcommand sees its arguments — they can appear anywhere on the command line, work identically across every tool, and are stripped out before per-command flag parsing runs.

--version (-v) and --help (-h) are also recognized on uip and every subcommand, but they are standard CLI conventions rather than global flags in the sense above.

Choose the output format. Both --output json and --output=json work; values are case-sensitive.

Only the five format names above are read as the global option. Several commands own a -o, --output <path> option of their own; a value that is not a format name, such as --output ./report.pdf, is left for the command. You can therefore combine a format and a command's output path in one invocation, for example --output json -o ./report.pdf.

Select a named, saved login profile instead of the default credentials location:

--profile <name> and a command's own -f, --file <folder> are mutually exclusive — passing both fails with ValidationError: option '--profile' cannot be used with option '--file'. Profile names are normalized (case and separator rules apply); an invalid name is rejected before any network call. See Sessions and credentials — named profiles.

Override the default "prompt only when stdout is a TTY" behavior:

--interactive sets prompting to always-on; --no-interactive forces it off. Neither flag is specific to uip login — despite appearing in login examples throughout this documentation set, interactivity is a cross-cutting global option with no command-specific short form (there is no --it or similar alias anywhere in the CLI).

--output controls stdout only. Logs, progress indicators, and human-facing errors go to stderr, regardless of format. This means a pipeline can capture clean JSON with:

…and still see the log output separately.

Apply a JMESPath expression to the Data field of the response envelope before formatting. The expression starts at Data, not at the envelope, so [*].Name picks names out of a Data array and length(@) returns a count. The result replaces Data; Result, Code, and the other envelope fields stay in place.

Keys in the filtered result are normalized to PascalCase, the same as unfiltered Data. A projection that returns plain values, such as [*].Name, is rendered as one record per value, keyed by the last field name in the expression.

Combining with --output:

A malformed filter expression fails fast with a ValidationError and exit code 3 before the underlying command runs — so a typo does not waste an API call.

The filter runs on the client, over the records the command fetched. On a command whose --limit has a default value, --output-filter requires an explicit --limit; without one, the command fails instead of filtering only the first page of records.

When the filter returns nothing, or only null values, from records that were there, the envelope carries a Warning field that names the fields the expression read that do not exist, and lists the available fields. The same note is written to stderr.

On failure, the filter is applied to the failure envelope's Data the same way. Message, Instructions, ErrorCode, Retry, and Context are never filtered. If the filter cannot be evaluated against a failure's Data, Data is shown in full and Warning explains why.

Set the verbosity of log messages (written to stderr, or to --log-file if provided).

Values are case-insensitive. Unknown values are silently ignored (the default is kept) rather than erroring — on purpose, so a typo in a wrapper script does not break a pipeline.

The UIPATH_LOG_LEVEL environment variable is not honored; pass the flag or set it in a profile script.

Write the log stream to the specified file instead of stderr. The file is created if it does not exist, including missing parent directories, and is truncated at the start of each run — use a build-specific path if you need to keep logs from several runs.

Each line in the file is the log message prefixed with an ISO 8601 timestamp:

Debug, warning, and error lines carry a [DEBUG], [WARN], or [ERROR] tag; info lines carry none. When --log-file is set, every envelope includes a Log field with the file path.

Global options are stripped from the command line before per-command flags are parsed, so they can appear anywhere on the command line:

All four invocations are equivalent.

Tool subcommands do not define their own --log-level. Commands that take an output path define -o, --output <path>; the CLI reads --output as the global option only when its value is one of the format names, so the two do not collide.

Global options control output and logging only; they do not affect exit codes. See Exit codes.

These environment variables change global-option behavior without a flag:

Set UIP_TIMINGS=1 (or true) and every invocation prints one line to stderr (or to the --log-file file, when one is set):

startup + command + flush always equals total. Fields are omitted when they don't apply: a run that never reaches a handler (uip --version, an unknown command) prints only total and exit; a command that makes no HTTP call has neither http nor httpCalls.

The report has its own switch — it doesn't depend on --log-level, so you get durations without turning on debug output, and stdout is never touched.

To keep the report off stderr without moving the rest of the log stream, set UIP_TIMINGS_FILE to a file path. Each invocation appends its line to that file, so several runs can share one file. Only the values 1 and true turn the report on; any other UIP_TIMINGS value leaves it off.