# Troubleshooting and FAQ

> Solutions for common setup and runtime issues with the uip CLI and UiPath skills, including installation failures, login problems, and unrecognized skills.

This page lists the issues people hit most often when setting up and using UiPath for Coding Agents, organized by the symptom you see.

## The installer fails partway through

If the one-liner stops with an error, read the message on screen — the installer writes its status and errors to the terminal.

- If a single runtime failed, re-run the installer. Each step is idempotent and skips what already succeeded.
- If you do not need the .NET SDK or Python yet, re-run with `--skip-runtimes` to get the CLI and skills in place first.

## "uip: command not found" after installing

If `uip` is not recognized, your `PATH` has not picked up the new install.

1. Open a new terminal so the updated `PATH` takes effect.
2. Run `uip --help` again to confirm.

## uip login does not complete

If the browser does not open or the login does not finish:

- Confirm you can reach your UiPath environment in a browser.
- If you use an environment other than `cloud.uipath.com`, pass it explicitly: `uip login --authority "https://your-environment"`.
- If the wrong tenant is selected, run `uip login -it` and choose the correct one.

## Your agent does not seem to use the skills

If your coding agent acts as though it does not know UiPath:

1. Confirm the skills installed by running `uip skills install` again.
2. Confirm your agent is one of the supported ones (see [Choosing your agent](choosing-your-agent.md)).
3. Restart your coding agent so it reloads its installed skills.

## A runtime is missing when you build

If a build fails because Node.js, the .NET SDK, or Python is missing, re-run the installer without any skip flags so it installs the runtimes it previously skipped.

## Getting more help

For deeper investigation, your coding agent can use the `uipath-troubleshoot` skill to diagnose a specific failure. To report a bug or suggestion, ask it to use `uipath-feedback`, or run the feedback command directly.
