REPO= Set up Agents from Conductor Cloud on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/migrate-conductor-cloud.md from top to bottom. The values at the top of this message are mine: - REPO: a GitHub repository you used in Conductor Cloud, as owner/name; add the others the same way afterwards Ask me for any that still say before you need them. The recipe's example VM name is my-agents. This VM's name is the output of `hostname`: use it wherever the recipe writes my-agents. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Claude Code and Codex connected to exe.dev's LLM integration, with no API key on the VM. - T3 Code running as a background service on port 3773, back after a reboot. - REPO cloned into `~/` through the GitHub integration and added to T3 Code as a project. - A `t3.json` in the clone that carries over the repository's Conductor setup script, if it has one, ready to import in T3 Code's Actions menu. - A setup-check thread in T3 Code that answers `OK`. Read the whole recipe, including the closed details. Follow "Set up by hand" from "Install T3 Code" to the end, as exedev; the walkthrough above it is for the owner. If `exeuntu configure` reports an existing user config, leave it alone. Do not create a pairing link: they expire in five minutes and work once. Leave public sharing off. REPO is a GitHub repository; turn a URL into owner/name. Clone it through the GitHub integration into ~/NAME. If that fails with "not found" or a 403, give the owner the integration command from "Get your code", with this VM's name, and wait for them; install the rest meanwhile. Look for a Conductor setup script in .conductor/settings.toml or conductor.json at the repository root. If there is one, write t3.json as "Setup and run scripts" says, translating CONDUCTOR_ variables; do not commit it and never push. If the owner's setup script lives only in Conductor's Cloud Computer settings, say that they need to paste it. Don't copy or invent .env files: the owner brings those. Finish by giving the owner the `ssh ... t3 pair` command from "Open T3 Code" with this VM's name, the integration command for their other repositories, and the list in "Before November 13" if it isn't November 13 yet. Finish with the URLs I should open.