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

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

You are done when all of these are true. Check each one yourself:
- The OpenMausBot web app at `https://<vm>.exe.xyz/`, behind your exe.dev login, with this browser paired as the owner.
- Claude bots through exe.dev's LLM integration, with no API key to paste.
- A server that stays on when you disconnect and starts again after a reboot, so routines keep running.
- The bots' built-in browser, installed and checked.
- Docker ready for the bots' private Linux desktop.

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. Install exactly the pinned
version. Do not run the restore or update instructions, and don't set
up a second VM unless the owner asks.
Keep the VM private. Never run share set-public, change the server's
loopback address, or set OMB_LOOPBACK_TRUST. On an existing VM, ask
before replacing configuration or a service on port 8000.
Verify `openmausbot doctor` says ready with the browser installed, a
`pong` from `openmausbot run`, the service enabled and active, and the
health check through nginx. Do not reboot.
Generate the pairing link last, after the owner has signed in to
https://<vm>.exe.xyz/. Give only the https://<vm>.exe.xyz/pair link and
explain that it works once and expires in five minutes; reissue on
request. The private desktop is prepared in the web app's settings:
point the owner to "Give it a desktop".

Finish with the URLs I should open.