# Install and connect Hilo

Paste the prompt below into a coding agent on the machine where Hilo agents will run.
Its job is deliberately narrow: install the node, join it to the customer's Hilo
workspace with the one-time file from Hilo Agents (Add a computer), run doctor, and stop.
Agent creation and import happen later in Hilo Agents.

> Design rule (why this file is shaped like this): the install itself must be
> **identical every time** — that's `install/install.sh`'s job. The agent adds
> confirmation and verification around it. If your agent starts
> improvising package installs or service files by hand, stop it and point it back at
> the script.

---

## The prompt — copy from here

```
You are installing Hilo on the machine where the customer's agents will run, and joining
that machine to the customer's Hilo workspace. The customer signed in at
https://agents.hilo.team, chose Add a computer, and downloaded the one-time
`.hilo-cloud-connection` file there. This document is the complete procedure: do not
fetch another guide or improvise extra setup.

0. CONFIRM THE MACHINE. Print `hostname` and `uname -sm`, show the result, and ask:
   "Is this the machine where your Hilo agents should run?" Wait for yes before changing
   anything. Do not scan this machine for agents, instructions, memory, skills, schedules,
   credentials, or project directories.

1. LOCATE THE CONNECTION FILE. Look only in the customer's Downloads folder for files
   whose name ends in `.hilo-cloud-connection`. If there is exactly one, show its path and
   ask the customer to confirm it. If there are zero or multiple matches, ask which exact
   path to use. Never print, open, paste, summarize, or reveal the file's contents. A file
   ending in `.hilo-connection` (without "cloud") is from Hilo's retired sign-in door and
   cannot work: ask the customer to download a new file from Add a computer instead.

2. RUN THE ONE INSTALL COMMAND. Replace `<exact-path>` below with the confirmed path,
   shell-quote that real path, and then run it. Never type the angle-bracket placeholder
   itself: `<...>` is shell redirection, not a filename.

       curl -fsSL https://get.hilo.team | sh -s -- --connection-file '<exact-path>'

   This downloads Hilo's current release, installs its background service, joins this
   machine to the workspace with the one-time file, restarts the service so it starts
   syncing, and runs doctor. Do not add `--admin`: customers sign in with their Hilo
   email and password, and this flow deliberately creates no local sign-in key.

3. WAIT FOR COMPLETION. Installing and joining usually takes a few minutes; the first
   install builds a Python environment, and the join waits for the restarted service to
   answer. Keep the command in the foreground and relay its progress lines to the
   customer. Do not start a second install or join, poll with separate shell commands, or
   conclude that the process is hung while it is still printing.

4. REPORT ONLY VERIFIED RESULTS. When the command exits successfully, report the Hilo
   version it installed, the computer name it joined as, and that doctor passed. If it
   fails, quote only the ordinary error message; never reveal the connection file or any
   credential material. Running the same command again is safe: a computer that already
   joined is not joined twice. End a successful report with this explicit next step:
   "Go to https://agents.hilo.team now, open this computer, and create or connect its
   first agent."

STOP HERE. Do not connect Claude Code, create an agent, import an existing agent, or edit
any agent files. Hilo Agents (https://agents.hilo.team) owns the next decision and guides
the customer through the runtime sign-in when they create or connect an agent there.
```

## After the install

- Open agents.hilo.team and sign in with your Hilo email + password, then open this
  computer. Creating an agent there walks through its runtime sign-in (Claude Code or
  OpenAI Codex); connecting an existing Claude Code agent takes its exact directory. Offer
  the agent to your workspace from its page; a workspace admin approves it at
  app.hilo.team.
- Managed tier (the ops agent) is a separate, later provision — the node ships with
  `entitlements.managed = false` and no ops-agent code (decision D10).
- Uninstall: `install/uninstall.sh` (keeps your data; `--purge` trashes it).
