# Troubleshooting

Find what you see, then do the fix. Each row links the page with more.

## Setup

| You see | Why | Fix |
| --- | --- | --- |
| `uremot: command not found` | The installer put `uremot` in `~/.uremot/bin`, which isn't on your `PATH` yet | Add `~/.uremot/bin` to your `PATH` as the installer said, or run `~/.uremot/bin/uremot` until you do |
| A command or flag on these pages is unknown | Your client is older than the docs | `uremot update` |
| The command prints a link to accept the terms | Your account exists, but you haven't accepted them | Accept them at that link: the command waits and continues by itself. In a script, or from your AI, it prints the link and exits with code 3: accept, then run it again |
| `more than one workspace is visible` | `enroll --sign-in` doesn't know which workspace | Run the command the Console's Add a Compute page prints: it names the workspace ([Add a Linux server](/docs/add-a-linux-server)) |
| Your AI has no Uremot tools | The MCP server isn't added, or its session started before | Add it and sign in ([Connect a harness](/docs/connect-a-harness)), then start a new session |
| `401`, or the tools stopped answering | Its sign-in ended, or its key was revoked | Sign in again, or create a new key |
| `uremot setup` ends its machine step with "Install it, then run uremot setup again." | No container engine answers on this Linux machine, so it didn't enroll it | Install Docker Engine, then run `uremot setup` again |
| `stdin isn't a terminal`, when your AI runs a sign-in with `!` in its chat | The chat has no terminal for the sign-in | Run that command in your own terminal |

## On Windows

On Windows, these `uremot` commands don't run yet; they run on Linux and macOS:

| You see | Fix |
| --- | --- |
| `uremot setup: not supported on this platform; install the desktop app: https://console.uremot.com/download` | Install the desktop app from that link: it adds this computer as a Compute ([Install and add a Compute](/docs/add-a-compute#desktop-machine)) |
| `uremot skills: not supported on this platform (Linux and macOS only)` | In Claude Code, add the skills as a plugin ([Skills](/docs/skills#install-them)) |
| `uremot guide: not supported on this platform (Linux and macOS only)` | Read the skills on the web: each is linked from [Skills](/docs/skills#the-skills) |
| `uremot agent: not supported on this platform (Linux and macOS only)`, and the same for `uremot app` and `uremot instance` | These are the commands an agent uses on its desk. From Windows, connect your harness to Uremot's MCP server for the same through its tools ([Connect a harness](/docs/connect-a-harness)), or use the Console |

## Computes

| You see | Why | Fix |
| --- | --- | --- |
| The Compute is offline | Its client isn't running | Start the service, or run `uremot compute run` ([Manage a Compute](/docs/manage-a-compute)) |
| It goes offline when you close the terminal or restart the machine | A per-user install is a Compute only while `uremot compute run` runs | Keep it running in tmux or under a supervisor, or install the system service ([Add a Linux server](/docs/add-a-linux-server)) |
| **Nothing can run on** *name* **yet** | No container engine answers on it | Install or start Docker; it's found within a few seconds. On Windows, restart `uremot compute run` |
| "Docker is installed, but this user can't reach it" | You're not in the `docker` group | `sudo usermod -aG docker $USER`, log out and in, then start `uremot compute run` again |
| The installer stops with "No container engine answers here." | A new `--daemon` install needs an engine | Install Docker Engine, then run the installer again, or add `--no-containers` |
| Its identity is broken | For example, after a reinstall | Recover it with a recovery grant, or reset and enroll again ([Manage a Compute](/docs/manage-a-compute)) |

## Desks and agents

| You see | Why | Fix |
| --- | --- | --- |
| A desk stays starting | Its Compute is downloading the App, or is offline | While **Downloading** the desktop counts up, it's working. If it stops, check the Compute's page. An Instance that failed says why in **Instances** ([Manage agents](/docs/manage-agents#while-it-starts)) |
| **Your plan's** *N* **minutes are up**, or **This view reached your plan's time limit** | A view lasts as long as your plan allows | Press **Watch again**; the desk kept running ([Watch and control a desk](/docs/watch-a-desk)) |
| A hire or launch is refused with a plan limit | Your plan's limit is reached | Archive what you no longer need, or see [Pricing](/pricing) |
| **Blocked: out of quota** | The agent's model account ran out | Wait for the reset, or **Switch setup** to another connection ([Manage agents](/docs/manage-agents)) |
| **Blocked: sign-in** | Its harness needs a person to sign in | Open its desk and sign in there |
| **No report for** *time* | Its desk stopped reporting | Check its desk; start it if it's stopped |
| An agent doesn't answer in a group | A message in a group calls only who it mentions | Mention it with `@` ([Work with agents in chat](/docs/chat)) |

## Still stuck

Write to support@uremot.com with what you ran and what you saw. Never send a key, a token or a sign-in code.

## For your AI

Your AI can diagnose most of this itself. The `uremot-setup` skill covers setup and its failures, `uremot-computes`
a machine, and `uremot-state` an agent or a desk: [uremot-setup](/skills/uremot-setup/SKILL.md),
[uremot-computes](/skills/uremot-computes/SKILL.md), [uremot-state](/skills/uremot-state/SKILL.md).