# LucidAgents setup guide (for Claude)

You are setting up LucidAgents for a tester on their Mac, in the folder this session is
open in. The person may never have used a terminal. Speak plainly, one step at a time,
and say what each step does before you run it. Never ask them to type a command or edit
a file, and **never ask for, accept or repeat a key in this chat**. Keys go into files
directly, and this guide's script writes the LucidPro key without showing it.

They gave you an invite code in their message (`LA-XXXX-XXXX-XXXX`). If it's missing,
ask for it; the code alone is fine to type here (it works once).

## 1. Check the folder and the Mac

- `uname -s` must be `Darwin`. If it isn't, stop: LucidAgents runs on macOS only.
- The folder must be empty: `ls -A` shows nothing, or only `.claude` (holding just
  `settings.local.json`) or `.DS_Store`.
  - If `.lucid/installed.json` exists, LucidAgents is already here. Say so, and offer
    to check the setup instead (step 3).
  - Otherwise ask them to make a new, empty folder named `LucidAgents` in their home
    folder and start a new Code session there. Then stop.
- Free disk: `df -g ~ | tail -1` must show about 5 GB available (column 4). If it
  doesn't, say how much they need to free up.

## 2. Fetch LucidAgents

Download the bootstrap script into a temporary folder, check it against this guide's
pinned checksum, and run it in this folder with the invite code:

```bash
T="$(mktemp -d)"; curl -fsSL https://get.lucidpro.ai/bootstrap.sh -o "$T/bootstrap.sh" \
  && echo "492921b9d487d484caeb23d022feec23f0a037801518581e20b7950a31bcc191  $T/bootstrap.sh" | shasum -a 256 -c - \
  && bash "$T/bootstrap.sh" "<invite code>"
```

- Tell them it downloads LucidAgents (about 60 MB) and a private copy of Python, which
  takes a minute or two.
- **If the checksum check fails, stop.** Don't run the script. Tell them to contact
  LucidPro.
- The script prints status lines only. On failure it prints `FAILED (<code>)`:
  - **40:** the invite code was refused (already used, expired or mistyped). Read
    them the reason and ask them to check the code with LucidPro.
  - **41:** no release is available yet. Ask them to try again later.
  - **11, 12:** the folder isn't empty, or is already an install (see step 1).
  - **20, 21, 22:** network or download trouble. Check the connection with
    `curl -sI https://get.lucidpro.ai`, then rerun the same command once.

## 3. Hand over to the shipped setup skill

The release is now unpacked here. This session started before those files existed, so
don't invoke the skill by name. Read `.claude/skills/setup/SKILL.md` and follow it from
the top. It installs the rest of the tools and the LucidAgents app, checks everything,
and ends with the app open.