← ClaudeAtlas

uremot-setuplisted

Set up Uremot from nothing to a first running Instance, or find out why it doesn't work. Use when a person asks to set up or start using Uremot, connect a harness to it, or install its client and skills, and when a command, a sign-in, a machine or a launch fails.
uremot/skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill uremot/skills
# Uremot setup Go in order and skip what already works: each step says how to check it. The goal is a first agent at work on the person's machine. Sign-ins and keys are the person's: they approve them in their own browser or terminal, and you never ask for one in chat or put one in a command. ## 1. What the machine needs Say this before anything is installed. On Linux, a Compute runs its desks in a container engine: `docker info` must answer (Docker Engine, https://docs.docker.com/engine/install/). On macOS or Windows, the machine joins with the Uremot desktop app (https://uremot.com/download) and runs desks with Docker Desktop. You may install or start the engine yourself: show the person the exact command first, and run it once they say yes. Where you can't get root (`sudo` asks for a password, or your sandbox refuses), give them that command and the link for their own terminal, and wait until they say it's done. Never ask for a password in chat. `sudo -n true` tells you which, without a prompt: it exits 0 when root is yours, and fails at once with "a password is required" when it isn't. ## 2. An account The person signs in at https://console.uremot.com with GitHub or Google. The first sign-in makes their organization and a Default workspace, and asks them to accept the terms. `uremot compute enroll --sign-in` signs in from a terminal and creates the account too, but answers `terms_not_accepted` until the terms are accepted in the Console, so send the person there firs