TELEGRAM_BOT_TOKEN= Set up nanobot on this VM by following the exe.dev recipe at https://exe.dev/deploy/nanobot.md?via=terminal from top to bottom. The values at the top of this message are mine: - TELEGRAM_BOT_TOKEN: optional; from @BotFather's `/newbot` in Telegram. Leave it as is to skip Telegram Ask me for any that still say before you need them. The recipe's example VM name is my-nanobot. This VM's name is the output of `hostname`: use it wherever the recipe writes my-nanobot. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - A private WebUI at `https://.exe.xyz/` that signs you in with your exe.dev login, with no second password. - Claude through exe.dev's LLM integration, with no API key to paste, and GPT a `/model gpt` away. - A gateway that stays on when you disconnect and starts again after a reboot, so scheduled tasks keep running. - Nightly backups of memory, conversations, schedules, and settings in `~/backups/nanobot`. - If you gave a bot token, a Telegram bot that answers only the accounts you approve. 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, and don't change the tool settings in "Rein in its tools" unless the owner asks. Telegram is optional. If TELEGRAM_BOT_TOKEN is empty or still says , skip Telegram and don't ask for it. Otherwise follow "Connect Telegram by hand", setting TG_TOKEN to the supplied token instead of the interactive read. If the log says the token was rejected, set channels.telegram.enabled to false, restart the gateway, and tell the owner. Never echo the bot token back. Keep the VM private. Never run share set-public or share add, bind the WebUI to a non-loopback address, or change trustedProxyAuth. On an existing VM, ask before replacing configuration or a service on port 8000. Verify a model reply, the gateway enabled and active, Linger=yes, the health check ready, the bootstrap answering 403 without the login header and 200 with it through nginx, the backup timer, and a tested archive. Do not reboot. Finish with the WebUI URL. If Telegram is connected, tell the owner to message the bot and approve its pairing code in the WebUI. Finish with the URLs I should open.