ANTHROPIC_ENVIRONMENT_ID=<fill-this-in>
ANTHROPIC_ENVIRONMENT_KEY=<fill-this-in>
EXE_TOKEN=<fill-this-in>

Set up Claude Managed Agents on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/claude-managed-agents.md from top to bottom.

The values at the top of this message are mine:
- ANTHROPIC_ENVIRONMENT_ID: your self-hosted environment's ID, `env_...`
- ANTHROPIC_ENVIRONMENT_KEY: its key, `sk-ant-oat01-...`
- 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-claude-dispatcher. This VM's name is the output of `hostname`: use it wherever the recipe writes my-claude-dispatcher. 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 claude-dispatcher service, which gives each session in the environment a VM of its own
- The service restarted on failure and after a reboot
- The environment key and exe.dev API key in /etc/claude-dispatcher.env, mode 600
- `exe.dev key works` and `environment key works` in `journalctl -u claude-dispatcher`

Run "Set up the dispatcher by hand" from "On the VM", skipping VM
creation and SSH. The three inputs are secrets: put them only in
/etc/claude-dispatcher.env, and never print them. Don't start a session
or run the owner's commands: they need the owner's own keys. If the log
shows `401` or `invalid token`, tell the owner which key was refused.
Finish by pointing the owner to "Give it a task".

Finish with the URLs I should open.