EXE_TOKEN=<fill-this-in>

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

The values at the top of this message are mine:
- EXE_TOKEN: the exe.dev API key that `ssh exe.dev ssh-key generate-api-key` printed, `exe1....`
Ask me for any that still say <fill-this-in> before you need them.

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

You are done when all of these are true. Check each one yourself:
- The code interpreter at https://my-code-interpreter.exe.xyz/, private behind exe.dev login, as code-interpreter.service, restarted on failure and after a reboot
- The exe.dev API key in /etc/code-interpreter.env, mode 600, and on no other VM
- `curl -s localhost:8000/api/health` on the VM answers `"exe":"ok"` and `"llm":"ok"`
- A test question answered by code run in a sandbox VM, and that test conversation and its sandbox deleted

Run "Set up by hand" from "On the VM", skipping VM creation and SSH.
EXE_TOKEN is a secret: put it only in /etc/code-interpreter.env, and
never print it. If the health check shows 401 or `invalid token`, tell
the owner the key was refused and how to make one ("Before you start").
Then run "Check it from the VM". Finish by pointing the owner to "Ask
it something".

Finish with the URLs I should open.