Set up Kaneo on this VM by following the exe.dev recipe at https://exe.dev/deploy/kaneo.md?via=terminal from top to bottom. The recipe's example VM name is my-kaneo. This VM's name is the output of `hostname`: use it wherever the recipe writes my-kaneo. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Kaneo 2 with PostgreSQL at `https://my-kaneo.exe.xyz/`, behind your exe.dev login, restarted after a reboot. - Sign-in with exe.dev, through Dex: no Kaneo passwords. Your account becomes the admin; teammates you invite get theirs on their first visit. - Secrets generated on the VM in `~/kaneo/.env` (mode 600), which is also where the agents' API key goes. - The `kaneo` CLI and the `kaneo-mcp` MCP server on the VM, ready for Claude Code, Codex and Shelley once there's an API key. - Nightly database backups in `~/kaneo/backups`, keeping two weeks. Read the whole recipe, closed details included, and follow "Set up by hand" in order, skipping VM creation; the walkthrough above it is for the owner. Don't sign in to Kaneo or send requests with X-ExeDev headers other than the check as written: the first account becomes the instance admin, and that must be the owner. Don't make the VM public. The VM can't reach its own https://.exe.xyz, so check with http://localhost:8000 as written. Don't run Restore or Update. Finish with Kaneo's URL, tell the owner to open it first to become the admin (choosing "Continue with exe.dev" if Kaneo shows a setup form), and point them to "Connect your agents" for the API key. Finish with the URLs I should open.