Set up Twenty on this VM by following the exe.dev recipe at https://exe.dev/deploy/twenty.md?via=terminal from top to bottom. The recipe's example VM name is my-twenty. This VM's name is the output of `hostname`: use it wherever the recipe writes my-twenty. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Twenty 2.60 on PostgreSQL and Redis, back after a reboot. - A CRM only you and the people you share the VM with can reach, with Twenty's own accounts on top. - AI chat and agents through exe.dev's LLM gateway, with no API key. - API access for scripts and other VMs with a VM token and a Twenty API key. - Nightly backups of the database, uploaded files and encryption key, with a test restore. Read the whole recipe, including the closed details, and follow "Install by hand" first, skipping VM creation and SSH. The walkthrough before it is for the owner afterwards. Do not run the public webhook, Restore or Update instructions during setup. Work as exedev in ~/twenty. Never overwrite an existing ~/twenty/.env: it holds the encryption key. Do not create the Twenty workspace or any account; the first person to sign up becomes the admin, and that must be the owner. Leave sharing alone. Verify docker.service is enabled, all four containers run with restart unless-stopped, localhost:8000/healthz reports "status":"ok", the gateway answers from the server container, the backup timer is enabled, and the backup test passes. Do not reboot. Finish with the URL https://.exe.xyz/ and tell the owner to open it right away and create the workspace, since the first sign-up becomes the admin. Finish with the URLs I should open.