Set up HyperFrames on this VM by following the exe.dev recipe at https://exe.dev/deploy/hyperframes.md?via=terminal from top to bottom. The recipe's example VM name is my-hyperframes. This VM's name is the output of `hostname`: use it wherever the recipe writes my-hyperframes. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - HyperFrames 0.9.70 and its headless Chrome on the VM, with telemetry off, and a 20-second promo rendered to MP4 as a check. - The browser editor at port 3002, behind exe.dev login, kept running across reboots; its Export renders on the VM. - A render API on port 8000 with a random token kept in ~/render-api/env, checked with a render from a template with variables. - HyperFrames' skills installed for Claude Code, Codex and Shelley, with Claude Code and Codex on exe.dev's LLM integration. - Videos and renders on the VM's disk, in ~/videos and ~/renders. Read the whole recipe, including the closed details. For initial setup, run "Install by hand" from "Install Node.js and HyperFrames" (skip creating the VM and SSH), through "Check it". Work as exedev. Never overwrite an existing ~/render-api/env, and don't paste its token into the chat. If Claude Code or Codex settings already exist, leave them alone. Do not share the VM or make it public, and do not set up AWS Lambda or HyperFrames Cloud. Finish with the editor URL using this VM's name, where the check render went, and the command from "Render from anywhere" that prints the API token. Finish with the URLs I should open.