{
  "manifest_version": "1",
  "slug": "t3code",
  "title": "T3 Code",
  "headline": "Run T3 Code on a remote server",
  "description": "Run T3 Code on an always-on exe.dev VM and steer Claude Code and Codex from your phone or any browser. Private by default, no API keys to paste.",
  "category": "ai-agents",
  "tags": [
    "t3 code",
    "t3code",
    "mobile coding",
    "remote coding agents",
    "claude code",
    "codex",
    "paseo"
  ],
  "url": "https://exe.dev/deploy/t3code",
  "markdown_url": "https://exe-staging.dev/deploy/t3code.md",
  "upstream": {
    "website": "https://t3.codes",
    "source": "https://github.com/pingdotgg/t3code",
    "docs": "https://github.com/pingdotgg/t3code/tree/main/docs/user",
    "license": "MIT"
  },
  "example_vm_name": "my-t3code",
  "time": "5 minutes",
  "stack": [
    {
      "name": "T3 Code server",
      "detail": "the t3 command, run as a systemd user service",
      "port": 3773,
      "data": "~/.t3/userdata"
    },
    {
      "name": "Claude Code and Codex",
      "detail": "preinstalled; connected to exe.dev's LLM integration",
      "data": "~/.claude, ~/.codex"
    },
    {
      "name": "Your project",
      "data": "~/project"
    }
  ],
  "access": [
    {
      "url": "https://my-t3code.exe.xyz:3773/",
      "who": "private",
      "what": "T3 Code in your phone's or laptop's browser, after a one-time pairing link"
    },
    {
      "url": "ssh my-t3code.exe.xyz",
      "who": "private",
      "what": "your terminal, for pairing links and upkeep"
    }
  ],
  "delivers": [
    "T3 Code running as a background service on port 3773, back after a reboot",
    "Claude Code and Codex ready in T3 Code through exe.dev's LLM integration, with no API key to paste",
    "A Git project at `~/project`, added to T3 Code",
    "T3 Code's web app at port 3773, behind exe.dev login and T3 Code's own pairing"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20T3%20Code%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Ft3code.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-t3code.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-t3code.%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-%20T3%20Code%20running%20as%20a%20background%20service%20on%20port%203773%2C%20back%20after%20a%20reboot%0A-%20Claude%20Code%20and%20Codex%20ready%20in%20T3%20Code%20through%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20API%20key%20to%20paste%0A-%20A%20Git%20project%20at%20%60~%2Fproject%60%2C%20added%20to%20T3%20Code%0A-%20T3%20Code%27s%20web%20app%20at%20port%203773%2C%20behind%20exe.dev%20login%20and%20T3%20Code%27s%20own%20pairing%0A%0ARun%20the%20VM-side%20commands%20in%20%22Set%20up%20T3%20Code%22%20only.%20If%20%60exeuntu%20configure%60%0Areports%20an%20existing%20user%20config%2C%20leave%20it%20alone.%20Do%20not%20create%20a%20pairing%0Alink%3A%20they%20expire%20in%20five%20minutes%20and%20work%20once.%20Verify%20that%0A%60t3%20service%20status%60%20says%20installed%2C%20that%20%60ss%20-ltn%60%20shows%20%600.0.0.0%3A3773%60%2C%0Aand%20that%20the%20setup-check%20thread%20prints%20%60OK%60.%20Skip%20%22Prefer%20Paseo%3F%22%2C%20the%0Abackup%2C%20update%20and%20troubleshooting%20sections%2C%20and%20the%20FAQ.%20Finish%20by%0Agiving%20the%20owner%20the%20browser%20URL%20and%20the%20%60ssh%20...%20t3%20pair%60%20command%20from%0A%22Pair%20your%20browser%22%2C%20with%20this%20VM%27s%20name%2C%20and%20tell%20them%20to%20follow%20%22Add%0Ayour%20phone%22%20next.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/t3code/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up T3 Code on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/t3code.md from top to bottom.\n\nThe recipe's example VM name is my-t3code. This VM's name is the output of `hostname`: use it wherever the recipe writes my-t3code. 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- T3 Code running as a background service on port 3773, back after a reboot\n- Claude Code and Codex ready in T3 Code through exe.dev's LLM integration, with no API key to paste\n- A Git project at `~/project`, added to T3 Code\n- T3 Code's web app at port 3773, behind exe.dev login and T3 Code's own pairing\n\nRun the VM-side commands in \"Set up T3 Code\" only. If `exeuntu configure`\nreports an existing user config, leave it alone. Do not create a pairing\nlink: they expire in five minutes and work once. Verify that\n`t3 service status` says installed, that `ss -ltn` shows `0.0.0.0:3773`,\nand that the setup-check thread prints `OK`. Skip \"Prefer Paseo?\", the\nbackup, update and troubleshooting sections, and the FAQ. Finish by\ngiving the owner the browser URL and the `ssh ... t3 pair` command from\n\"Pair your browser\", with this VM's name, and tell them to follow \"Add\nyour phone\" next.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/t3code/prompt.txt"
  },
  "updated": "2026-10-30",
  "verified": "2026-10-30",
  "related": [
    "claude-code",
    "codex",
    "opencode",
    "exe-mcp",
    "openclaw",
    "pi"
  ]
}