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

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

You are done when all of these are true. Check each one yourself:
- magpie running in Docker Compose on ports 3425 and 3430, bound to the VM's loopback and back after a reboot
- A web key in `~/magpie/.env`, readable only by you, and magpie's settings on the VM's disk in `~/magpie/config`
- exe.dev's LLM integration added to magpie as two providers, with no API key, and a routing group `group/open-models` that fails over from Kimi K3 to GLM-5.3 to DeepSeek V4.1 Flash
- A gateway key for this VM in `~/magpie/this-vm.key`, and Claude Code on the VM answering through `group/open-models`
- The web UI at `https://<vm>.exe.xyz:3430/`, private to you

Run the VM-side commands in "Install by hand" only, skipping VM
creation. Never run share set-public or share port, never publish 3425
or 3430 beyond 127.0.0.1, and never sign magpie in to a subscription
(`magpie accounts add`, Claude, ChatGPT and the like). Verify that
`docker compose ps` shows the container healthy, that
`curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3425/v1/models`
prints 401, and that the Claude Code check prints OK. Never print the
gateway key in your messages. Finish by giving the owner the web UI
link from "Open the web UI" with this VM's name and its ?k= key (this
conversation is private to them), and point them to "Use it from your
laptop" and "Use it from your other VMs", which they set up on their
own computer.

Finish with the URLs I should open.