{
  "manifest_version": "1",
  "slug": "rex",
  "title": "Rex",
  "headline": "Run a Rex server on a remote Linux VM",
  "description": "Run the Rex server (beta) on an always-on exe.dev VM and add it to Rex for Mac over SSH: sessions and agents keep running when your Mac sleeps.",
  "category": "ai-agents",
  "tags": [
    "rex",
    "superlogical",
    "terminal multiplexer",
    "rex server",
    "remote host",
    "ssh",
    "tailscale",
    "claude code",
    "codex"
  ],
  "url": "https://exe.dev/deploy/rex",
  "markdown_url": "https://exe-staging.dev/deploy/rex.md",
  "upstream": {
    "website": "https://www.superlogical.com/rex",
    "docs": "https://www.superlogical.com/rex/docs/linux/installation",
    "license": "Proprietary (free beta)"
  },
  "example_vm_name": "my-rex",
  "time": "5 minutes",
  "stack": [
    {
      "name": "Rex server",
      "detail": "the rex package (0.1.0 preview), a personal server run as your account by systemd",
      "data": "~/.local/state/rex"
    },
    {
      "name": "Claude Code and Codex",
      "detail": "preinstalled; connected to exe.dev's LLM integration, with Rex's agent skill",
      "data": "~/.claude, ~/.codex"
    },
    {
      "name": "Your project",
      "data": "~/project"
    }
  ],
  "access": [
    {
      "url": "ssh://my-rex.exe.xyz",
      "who": "private",
      "what": "the Rex server, for Rex for Mac and the rex command; your exe.dev SSH key gets you in"
    },
    {
      "url": "ssh my-rex.exe.xyz",
      "who": "private",
      "what": "your terminal"
    }
  ],
  "delivers": [
    "Rex's Linux server from the preview channel, running as `exedev` and back after a reboot",
    "Rex for Mac reaching it over SSH, with the key you already use for exe.dev",
    "Claude Code and Codex using exe.dev's LLM integration, with Rex's agent skill installed",
    "A Rex session `work` in `~/project` where Claude Code answers `OK`"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Rex%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Frex.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-rex.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-rex.%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-%20Rex%27s%20Linux%20server%20from%20the%20preview%20channel%2C%20running%20as%20%60exedev%60%20and%20back%20after%20a%20reboot%0A-%20Rex%20for%20Mac%20reaching%20it%20over%20SSH%2C%20with%20the%20key%20you%20already%20use%20for%20exe.dev%0A-%20Claude%20Code%20and%20Codex%20using%20exe.dev%27s%20LLM%20integration%2C%20with%20Rex%27s%20agent%20skill%20installed%0A-%20A%20Rex%20session%20%60work%60%20in%20%60~%2Fproject%60%20where%20Claude%20Code%20answers%20%60OK%60%0A%0ARun%20the%20VM-side%20commands%20in%20%22Set%20up%20the%20VM%22%20only%3B%20skip%20creating%20the%20VM.%0AIf%20%60exeuntu%20configure%60%20reports%20an%20existing%20user%20config%2C%20leave%20it%20alone.%0AIf%20%60~%2Fproject%60%20already%20exists%2C%20leave%20it%20alone.%20Don%27t%20start%20interactive%0Aagents.%20Verify%20with%20the%20checks%20at%20the%20end%20of%20that%20section%3A%20%60rex%20version%60%0Astarts%20with%20%60rex%200.1.0%60%2C%20%60rex%20server%20status%60%20shows%20%60exit-empty%3A%20false%60%2C%0Aand%20the%20%60work%60%20session%20shows%20%60OK%60%20from%20Claude%20Code.%20Skip%20the%20later%0Asections%20and%20the%20FAQ.%20Finish%20by%20telling%20the%20owner%20to%20run%0A%60ssh%20%3Cthis%20VM%27s%20name%3E.exe.xyz%20rex%20version%60%20on%20their%20Mac%2C%20then%20add%0A%60ssh%3A%2F%2F%3Cthis%20VM%27s%20name%3E.exe.xyz%60%20in%20Rex%20for%20Mac%20with%0A%2A%2AAdd%20Remote%20Host%E2%80%A6%2A%2A%20%28%22Add%20it%20to%20Rex%20for%20Mac%22%29.%20Never%20put%20Rex%20behind%0Aexe.dev%27s%20HTTPS%20proxy%20or%20use%20%60--allow-anonymous%60.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/rex/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Rex on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/rex.md from top to bottom.\n\nThe recipe's example VM name is my-rex. This VM's name is the output of `hostname`: use it wherever the recipe writes my-rex. 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- Rex's Linux server from the preview channel, running as `exedev` and back after a reboot\n- Rex for Mac reaching it over SSH, with the key you already use for exe.dev\n- Claude Code and Codex using exe.dev's LLM integration, with Rex's agent skill installed\n- A Rex session `work` in `~/project` where Claude Code answers `OK`\n\nRun the VM-side commands in \"Set up the VM\" only; skip creating the VM.\nIf `exeuntu configure` reports an existing user config, leave it alone.\nIf `~/project` already exists, leave it alone. Don't start interactive\nagents. Verify with the checks at the end of that section: `rex version`\nstarts with `rex 0.1.0`, `rex server status` shows `exit-empty: false`,\nand the `work` session shows `OK` from Claude Code. Skip the later\nsections and the FAQ. Finish by telling the owner to run\n`ssh \u003cthis VM's name\u003e.exe.xyz rex version` on their Mac, then add\n`ssh://\u003cthis VM's name\u003e.exe.xyz` in Rex for Mac with\n**Add Remote Host…** (\"Add it to Rex for Mac\"). Never put Rex behind\nexe.dev's HTTPS proxy or use `--allow-anonymous`.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/rex/prompt.txt"
  },
  "updated": "2026-11-16",
  "related": [
    "herdr",
    "orca",
    "claude-code",
    "codex",
    "t3code",
    "openclaw"
  ],
  "alternatives": [
    "tmux"
  ]
}
