- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip docsai
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- restore
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- Migration
- Reference & support
UiPath CLI user guide
uip codedapp builds, packs, publishes, deploys, and manages UiPath Coded Web Applications — HTML/JavaScript apps authored in Studio Web and hosted on UiPath Cloud. The verbs cover the full lifecycle: pull a remote project to local disk, push changes back, pack into a .nupkg, publish to UiPath, then deploy or upgrade the app. Install it with uip tools install codedapp, or invoke uip codedapp … and let auto-install run. See Tools (plugins) for the install model and uip tools for the command that manages tool installation. codedapp is the command prefix; the underlying package is @uipath/codedapp-tool.
The tool runs a pre-action hook on every command that reads the session written by uip login and exports it into the environment, so most auth-related flags are optional — they exist as one-off overrides.
Commands
Every uip codedapp verb has its own reference page. For live argument lists on your installed tool version, run uip codedapp <verb> --help.
Synopsis
uip codedapp pull [--project-id <id>] [--target-dir <dir>] [--overwrite] [<auth flags>]
uip codedapp push [--project-id <id>] [--build-dir <dir>] [--ignore-resources] [<auth flags>]
uip codedapp pack <dist> [--name <n>] [--version <v>] [--output <dir>] [...] [<auth flags>]
uip codedapp publish [--name <n>] [--version <v>] [--type <Web|Action>] [<auth flags>]
uip codedapp deploy [--name <n>] [--version <v>] [--folder-key <key>] [<auth flags>]
uip codedapp pull [--project-id <id>] [--target-dir <dir>] [--overwrite] [<auth flags>]
uip codedapp push [--project-id <id>] [--build-dir <dir>] [--ignore-resources] [<auth flags>]
uip codedapp pack <dist> [--name <n>] [--version <v>] [--output <dir>] [...] [<auth flags>]
uip codedapp publish [--name <n>] [--version <v>] [--type <Web|Action>] [<auth flags>]
uip codedapp deploy [--name <n>] [--version <v>] [--folder-key <key>] [<auth flags>]
Common auth-override flags on every subcommand: --base-url <url>, --org-id <id>, --tenant-id <id>, --access-token <token> (plus --org-name / --tenant-name where relevant). Prefer uip login — these flags are for one-off overrides.
All uip codedapp verbs honor the global options (--output, --output-filter, --log-level, --log-file). Standard exit codes apply.
See also
- Tools (plugins) — install model for
@uipath/codedapp-tool. uip login— credentials consumed by every subcommand.- Configuration — precedence of credentials (env vars → file → flags).