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

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

You are done when all of these are true. Check each one yourself:
- Google Chrome running all the time in a container, restarted if it closes or crashes and after a reboot
- The browser at `https://<vm>.exe.xyz:3000/`, behind exe.dev login, with sound, clipboard and file upload and download
- Chrome's DevTools protocol on `localhost:9222` and, behind exe.dev login, at `https://<vm>.exe.xyz:9222/`
- Playwright MCP on `localhost:8931`, registered with Claude Code, driving the same browser
- Logins, cookies and tabs kept in `~/browser/config` on the VM's disk

Run the VM-side command in "Set up by hand" (skip creating the VM),
then the commands in "Let an agent drive it" that connect Claude Code
to Playwright MCP, and check them with the `claude -p` command there.
If Claude Code settings already exist, add the MCP server without
replacing them. Never make the VM public or point port 8000 at port
3000 or 9222: the browser has no password of its own. Finish with the
browser's URL.

Finish with the URLs I should open.