{
  "manifest_version": "1",
  "slug": "migrate-conductor-cloud",
  "title": "Agents from Conductor Cloud",
  "headline": "Move from Conductor Cloud to your own always-on VM",
  "description": "Conductor Cloud goes read-only on November 13 and shuts down on November 20. Move your parallel coding agents and worktrees to an always-on exe.dev VM.",
  "category": "migration",
  "tags": [
    "conductor",
    "conductor cloud",
    "conductor alternative",
    "conductor meta",
    "parallel coding agents",
    "git worktrees",
    "t3 code",
    "claude code",
    "codex"
  ],
  "url": "https://exe.dev/deploy/migrate-conductor-cloud",
  "markdown_url": "https://exe-staging.dev/deploy/migrate-conductor-cloud.md",
  "upstream": {
    "website": "https://www.conductor.build",
    "source": "https://github.com/pingdotgg/t3code",
    "docs": "https://www.conductor.build/announcement",
    "license": "Proprietary (Conductor); MIT (T3 Code); your code is yours"
  },
  "example_vm_name": "my-agents",
  "time": "20 minutes",
  "stack": [
    {
      "name": "T3 Code",
      "detail": "A web app for parallel agents, one Git worktree per thread, as a systemd user service",
      "port": 3773,
      "data": "~/.t3/userdata; worktrees in ~/.t3/worktrees"
    },
    {
      "name": "Claude Code and Codex",
      "detail": "Preinstalled; connected to exe.dev's LLM integration, so no API keys on the VM",
      "data": "~/.claude, ~/.codex"
    },
    {
      "name": "Your repositories",
      "detail": "Cloned through the GitHub integration, with the branches you pushed from Conductor",
      "data": "~/\u003crepo\u003e"
    }
  ],
  "access": [
    {
      "url": "https://my-agents.exe.xyz:3773/",
      "who": "private",
      "what": "T3 Code in your browser or phone, after a one-time pairing link"
    },
    {
      "url": "https://my-agents.exe.xyz:3000/",
      "who": "private",
      "what": "A dev server an agent starts, on any port from 3000 to 9999"
    },
    {
      "url": "ssh my-agents.exe.xyz",
      "who": "private",
      "what": "Your terminal, for pairing links, .env files and upkeep"
    }
  ],
  "inputs": [
    {
      "name": "REPO",
      "description": "a GitHub repository you used in Conductor Cloud, as owner/name; add the others the same way afterwards"
    }
  ],
  "delivers": [
    "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 `~/\u003cname\u003e` 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`."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=REPO%3D%3Cfill-this-in%3E%0A%0ASet%20up%20Agents%20from%20Conductor%20Cloud%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fmigrate-conductor-cloud.md%20from%20top%20to%20bottom.%0A%0AThe%20values%20at%20the%20top%20of%20this%20message%20are%20mine%3A%0A-%20REPO%3A%20a%20GitHub%20repository%20you%20used%20in%20Conductor%20Cloud%2C%20as%20owner%2Fname%3B%20add%20the%20others%20the%20same%20way%20afterwards%0AAsk%20me%20for%20any%20that%20still%20say%20%3Cfill-this-in%3E%20before%20you%20need%20them.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-agents.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-agents.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Claude%20Code%20and%20Codex%20connected%20to%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20API%20key%20on%20the%20VM.%0A-%20T3%20Code%20running%20as%20a%20background%20service%20on%20port%203773%2C%20back%20after%20a%20reboot.%0A-%20REPO%20cloned%20into%20%60~%2F%3Cname%3E%60%20through%20the%20GitHub%20integration%20and%20added%20to%20T3%20Code%20as%20a%20project.%0A-%20A%20%60t3.json%60%20in%20the%20clone%20that%20carries%20over%20the%20repository%27s%20Conductor%20setup%20script%2C%20if%20it%20has%20one%2C%20ready%20to%20import%20in%20T3%20Code%27s%20Actions%20menu.%0A-%20A%20setup-check%20thread%20in%20T3%20Code%20that%20answers%20%60OK%60.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20Follow%20%22Set%20up%20by%0Ahand%22%20from%20%22Install%20T3%20Code%22%20to%20the%20end%2C%20as%20exedev%3B%20the%20walkthrough%0Aabove%20it%20is%20for%20the%20owner.%20If%20%60exeuntu%20configure%60%20reports%20an%20existing%0Auser%20config%2C%20leave%20it%20alone.%20Do%20not%20create%20a%20pairing%20link%3A%20they%20expire%0Ain%20five%20minutes%20and%20work%20once.%20Leave%20public%20sharing%20off.%0AREPO%20is%20a%20GitHub%20repository%3B%20turn%20a%20URL%20into%20owner%2Fname.%20Clone%20it%0Athrough%20the%20GitHub%20integration%20into%20~%2FNAME.%20If%20that%20fails%20with%20%22not%0Afound%22%20or%20a%20403%2C%20give%20the%20owner%20the%20integration%20command%20from%20%22Get%20your%0Acode%22%2C%20with%20this%20VM%27s%20name%2C%20and%20wait%20for%20them%3B%20install%20the%20rest%0Ameanwhile.%0ALook%20for%20a%20Conductor%20setup%20script%20in%20.conductor%2Fsettings.toml%20or%0Aconductor.json%20at%20the%20repository%20root.%20If%20there%20is%20one%2C%20write%20t3.json%0Aas%20%22Setup%20and%20run%20scripts%22%20says%2C%20translating%20CONDUCTOR_%20variables%3B%20do%0Anot%20commit%20it%20and%20never%20push.%20If%20the%20owner%27s%20setup%20script%20lives%20only%0Ain%20Conductor%27s%20Cloud%20Computer%20settings%2C%20say%20that%20they%20need%20to%20paste%20it.%0ADon%27t%20copy%20or%20invent%20.env%20files%3A%20the%20owner%20brings%20those.%0AFinish%20by%20giving%20the%20owner%20the%20%60ssh%20...%20t3%20pair%60%20command%20from%20%22Open%20T3%0ACode%22%20with%20this%20VM%27s%20name%2C%20the%20integration%20command%20for%20their%20other%0Arepositories%2C%20and%20the%20list%20in%20%22Before%20November%2013%22%20if%20it%20isn%27t%0ANovember%2013%20yet.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/migrate-conductor-cloud/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "REPO=\u003cfill-this-in\u003e\n\nSet 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.\n\nThe values at the top of this message are mine:\n- REPO: a GitHub repository you used in Conductor Cloud, as owner/name; add the others the same way afterwards\nAsk me for any that still say \u003cfill-this-in\u003e before you need them.\n\nThe 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.\n\nYou are done when all of these are true. Check each one yourself:\n- Claude Code and Codex connected to exe.dev's LLM integration, with no API key on the VM.\n- T3 Code running as a background service on port 3773, back after a reboot.\n- REPO cloned into `~/\u003cname\u003e` through the GitHub integration and added to T3 Code as a project.\n- 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.\n- A setup-check thread in T3 Code that answers `OK`.\n\nRead the whole recipe, including the closed details. Follow \"Set up by\nhand\" from \"Install T3 Code\" to the end, as exedev; the walkthrough\nabove it is for the owner. If `exeuntu configure` reports an existing\nuser config, leave it alone. Do not create a pairing link: they expire\nin five minutes and work once. Leave public sharing off.\nREPO is a GitHub repository; turn a URL into owner/name. Clone it\nthrough the GitHub integration into ~/NAME. If that fails with \"not\nfound\" or a 403, give the owner the integration command from \"Get your\ncode\", with this VM's name, and wait for them; install the rest\nmeanwhile.\nLook for a Conductor setup script in .conductor/settings.toml or\nconductor.json at the repository root. If there is one, write t3.json\nas \"Setup and run scripts\" says, translating CONDUCTOR_ variables; do\nnot commit it and never push. If the owner's setup script lives only\nin Conductor's Cloud Computer settings, say that they need to paste it.\nDon't copy or invent .env files: the owner brings those.\nFinish by giving the owner the `ssh ... t3 pair` command from \"Open T3\nCode\" with this VM's name, the integration command for their other\nrepositories, and the list in \"Before November 13\" if it isn't\nNovember 13 yet.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/migrate-conductor-cloud/prompt.txt"
  },
  "updated": "2026-11-07",
  "verified": "2026-11-07",
  "related": [
    "t3code",
    "orca",
    "paseo",
    "paradev",
    "herdr",
    "claude-code"
  ],
  "alternatives": [
    "Conductor Cloud"
  ]
}