Set up Gemini Managed Agents on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/gemini-managed-agents.md?via=terminal from top to bottom. The recipe's example VM name is my-gemini-sandbox. This VM's name is the output of `hostname`: use it wherever the recipe writes my-gemini-sandbox. 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 gemini-api CLI 0.4.6 in /usr/local/bin - The gemini-worker service, restarted on failure and after a reboot, giving the agent ~/workspace - No environment key on the VM; the worker reaches Google through `https://gemini-env.int.exe.xyz` - `Worker ... polling` in `journalctl -u gemini-worker` once the owner has added the gemini-env integration Run "Set up the worker by hand" from "On the VM", skipping VM creation and SSH. Install exactly the pinned version. Don't ask for or handle any key: the environment key goes into an exe.dev integration that only the owner can add, from their computer. Until they do, the log shows `integration not found or not attached to this VM`, which is expected; tell the owner to run the `integrations add` command from "Connect the worker" in the folder where they saved gemini-env.json, then check the log for `polling`. Don't change the VM's egress policy. Finish by pointing the owner to "Give it a task". 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 integrations add http-proxy --name gemini-env --target https://generativelanguage.googleapis.com --header "x-goog-environment-key:$(jq -r .environment_key gemini-env.json)" --attach vm:my-gemini-sandbox # in the folder with gemini-env.json