Set up Rex on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/rex.md from top to bottom.

The recipe's example VM name is my-rex. This VM's name is the output of `hostname`: use it wherever the recipe writes my-rex. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- Rex's Linux server from the preview channel, running as `exedev` and back after a reboot
- The server on your tailnet as `my-rex` once you open its Tailscale sign-in link
- Claude Code and Codex using exe.dev's LLM integration, with Rex's agent skill installed
- A Rex session `work` in `~/project` where Claude Code answers `OK`

Run the VM-side commands in "Set up the VM" only; skip creating the VM.
If `exeuntu configure` reports an existing user config, leave it alone.
If `~/project` already exists, leave it alone. Don't start interactive
agents. Verify with the checks at the end of that section: the service
is active, `rex version` starts with `rex 0.1.0`, and the `work` session
shows `OK` from Claude Code. Skip the later sections and the FAQ.
Finish by giving the owner the Tailscale sign-in link from
`rex server status` (the `authenticate:` line), and tell them to open it
signed in to the tailnet their Mac is on, check that MagicDNS and HTTPS
certificates are on for that tailnet, then add
`https://<this VM's name>.<tailnet>.ts.net` in Rex for Mac with
**Add Remote Host…** ("Add it to Rex for Mac"). Never put Rex behind
exe.dev's HTTPS proxy or use `--allow-anonymous`.

Finish with the URLs I should open.