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

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

You are done when all of these are true. Check each one yourself:
- QM at `https://<vm>.exe.xyz/`, behind your exe.dev login and QM's own sign-in, with you as its administrator.
- Claude through exe.dev's LLM integration, with no API key to paste, and GPT models in the admin console.
- Agent computers that run commands and keep their files, each in its own container on the VM.
- A stack that comes back by itself after a reboot.
- Nightly backups of the database, settings, and agent computers in `~/backups/qm`.

Read the whole recipe, including the closed details. For initial setup,
follow "Install by hand" first, skipping VM creation and SSH. The
opening walkthrough is for the owner. Do not run the restore or update
instructions.
Keep the VM private. Never run share set-public. On an existing VM, ask
before replacing anything already on ports 7999-8002 or a `~/qm` folder.
Skip `qm doctor`: it tests the placeholder key against Anthropic
directly and always fails here. Run `fix-local-sandbox.sh` after every
`qm up`.
Verify `qm check` passes, `{"ok":true}` from the health check, the
patch reports itself in place, the backup timer, and a backup archive.
Don't set up Slack unless the owner asks. Do not reboot.
Finish by running `npm exec qm -- admin-login` in `~/qm` and giving the
owner the link it prints, saying it works once and expires in five
minutes; this conversation is private to the owner.

Finish with the URLs I should open.