Set up with your AI

Your AI can set Uremot up for you: install the client, connect itself, add your machine, and hire your first agent. You approve each sign-in in your own browser. It never needs your password, a key or a code.

Start#

Press Set up with your AI on the home page or in the Console's header. It copies the setup text. Paste it into Claude Code, Codex or OpenCode on the machine you're setting up. The text itself is public: setup.txt.

The setup text asks your AI to show each command before it runs it and to skip what already works. It follows the uremot-setup skill once it has it (uremot-setup).

What happens#

1. It checks what the machine needs. On Linux, a container engine (docker info must answer). On macOS or Windows, the machine joins with the Uremot desktop app, and runs desks with Docker Desktop.

2. It installs the uremot client, or gives you the line to run:

   Terminal

   curl -fsSL https://get.uremot.com | sh

3. It installs Uremot's skills for itself (uremot skills install), then follows the uremot-setup skill. On Windows, uremot skills install doesn't run yet; the skill is public at uremot-setup, and Skills has another way to install it.

4. You sign in to the Console in your browser. A first sign-in creates your account and asks you to accept the terms.

5. It connects itself to Uremot's MCP server, and you approve that sign-in in your browser, choosing the organization and workspace it acts in. Then you restart it, so it loads Uremot's tools, and tell it to continue.

6. It adds your machine as a Compute, with your approval in the browser, or points you to the desktop app.

7. It hires your first agent with you and gives it a task. The agent thinks with your model account: if none is linked yet, you link one in the Console's Connections. You get a link to watch its desk.

uremot setup, from a terminal#

If you'd rather type, the installer ends by offering uremot setup, which does steps 4 to 6 in one go. It signs you in and adds this machine as your Compute. Then it connects each harness it finds here, with its own mcp add, the skills and its own sign-in. It runs on Linux and macOS:

uremot setup

It's safe to run again: it skips what's already done. It asks before it connects the harnesses it found.

What it never does: it holds no credential, prints none, and never edits a harness's configuration itself. It runs each harness's own mcp add and sign-in.

On Linux, once it has enrolled the machine, a per-user install says Next: uremot compute run: the machine is a Compute only while that runs, so keep it in tmux or under a supervisor. On the system service's install, run as root, it starts the service instead (Add a Linux server).

With no container engine, it says what to install and doesn't enroll the machine: run it again once the engine answers. If Docker is installed but your user can't reach it, it says to join the docker group and log in again.

On macOS, the computer joins through the desktop app instead: uremot setup says so and still connects your harnesses. On Windows, use the desktop app.

When it's done#

uremot setup ends with: Done. Restart your harness, then ask it: "Set up my first Uremot agent."

If something stops it, see Troubleshooting. To do every step yourself instead, see Getting started, by hand.