Set up goose on this VM by following the exe.dev recipe at https://exe.dev/deploy/goose.md from top to bottom.

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

You are done when all of these are true. Check each one yourself:
- goose connected to Claude and GPT through exe.dev, with no API key to paste
- A project folder at `~/project` on persistent disk
- A `goose` tmux session that survives disconnects
- goose's server with its recipe scheduler, on localhost only, back after a reboot

Run the VM-side setup in "Start coding" and "Keep goose running". If
`~/.config/goose/config.yaml` already exists, set the provider and model
in it instead of replacing it. Create tmux detached
(`tmux new -d -s goose -c ~/project`) rather than attaching, and reuse
the session if it already exists. Do not launch interactive goose, do not
run `goose doctor` or `goose configure`, and do not schedule any recipe.
Verify from ~/project with
`goose run --no-session -t "Reply with exactly: OK" </dev/null`, check
`tmux has-session -t goose`, that `systemctl is-enabled goose` prints
`enabled`, and that `curl -s http://127.0.0.1:3284/status` prints `ok`.
Skip the later optional instructions and FAQ. Finish with the SSH command
from "Take a break", using this VM's name, and tell the owner to run
`goose session -n main` inside it.

Finish with the URLs I should open.