SLACK_USER_ID= GIT_NAME= GIT_EMAIL= Set up OpenComputer on this VM by following the exe.dev recipe at https://exe.dev/deploy/opencomputer.md?via=terminal from top to bottom. The values at the top of this message are mine: - SLACK_USER_ID: your Slack member ID (`U…`): in Slack, click your name, then ⋮ → Copy member ID. Only people listed in the gateway get sessions - GIT_NAME: the name on commits from your sessions - GIT_EMAIL: the email on commits from your sessions Ask me for any that still say before you need them. The recipe's example VM name is my-opencomputer. This VM's name is the output of `hostname`: use it wherever the recipe writes my-opencomputer. Skip the step that creates the VM; you are on it. This recipe needs a 50GB disk, and a new VM's may be smaller. Before you install anything, run `df -h /`. If its size is under 45G, stop and ask me to grow the disk, either with this link: https://exe.dev/suggest?command=resize%20my-opencomputer%20--disk%3D50GB or, on my computer, with `ssh exe.dev resize my-opencomputer --disk=50GB`. When I say it's done, run `sudo resize2fs "$(findmnt -no SOURCE /)"`, check `df -h /` again, and carry on. You are done when all of these are true. Check each one yourself: - The OpenComputer gateway and its nginx edge in Docker Compose, back after a reboot, with `/healthz` on port 3170 listing the VM under `hosts`. - The computer (host agent, client relay, and model proxy) as enabled systemd services. - Claude through exe.dev's LLM integration, by an `exe-llm` model-proxy profile, with no API key. - A workspace definition in `/etc/opencomputer`, ready for repositories cloned through exe.dev's GitHub integration. - Nightly backups of the gateway's database, secrets, and configuration in `~/opencomputer-backups`. Read the whole recipe, including the closed details. For initial setup, run "Install by hand" first, skipping VM creation and SSH, with the owner's SLACK_USER_ID, GIT_NAME and GIT_EMAIL. Run the provisioning command in the background or in tmux: it takes about five minutes. Do not run the restore or update instructions. Never print SETUP_TOKEN, SP_STORE_KEY or the host token, except the one setup link at the end. Do not create or install the Slack app yourself: the owner does that in a browser. Never run share set-public (the owner does); never publish port 3170 or the gateway's /setup or /host. Verify /healthz on port 3170 lists the VM under hosts, the services enabled and active, a reply from the model proxy's exe-llm profile, a 404 for / on port 8000, and a tested backup archive. Do not reboot. Finish with the steps of "Connect Slack", including the setup link from "Open the setup page" (this conversation is private to the owner), and "Give it your repositories". Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them): ssh exe.dev share set-public my-opencomputer