{
  "manifest_version": "1",
  "slug": "openclaw",
  "title": "OpenClaw",
  "headline": "Host OpenClaw",
  "description": "Give OpenClaw its own computer on exe.dev. Chat in a private dashboard, add Telegram when you like, and let your laptop take a nap.",
  "category": "ai-agents",
  "tags": [
    "openclaw",
    "clawdbot",
    "moltbot",
    "personal ai assistant",
    "telegram bot",
    "ai agent"
  ],
  "url": "https://exe.dev/deploy/openclaw",
  "markdown_url": "https://exe-staging.dev/deploy/openclaw.md",
  "upstream": {
    "website": "https://openclaw.ai",
    "source": "https://github.com/openclaw/openclaw",
    "docs": "https://docs.openclaw.ai",
    "license": "MIT"
  },
  "example_vm_name": "my-openclaw",
  "time": "15 minutes",
  "stack": [
    {
      "name": "OpenClaw Gateway",
      "detail": "Background service, managed by systemd",
      "port": 18789,
      "data": "~/.openclaw"
    },
    {
      "name": "nginx",
      "detail": "Private dashboard proxy",
      "port": 8000
    },
    {
      "name": "Claude",
      "detail": "Connected through exe.dev's LLM integration"
    }
  ],
  "access": [
    {
      "url": "https://my-openclaw.exe.xyz/",
      "who": "private",
      "what": "Your chat dashboard"
    }
  ],
  "delivers": [
    "A private dashboard that chats with Claude. No API key to paste.",
    "An assistant that stays on when you disconnect and starts again after a reboot.",
    "Nightly backups of your settings, conversations, and workspace."
  ],
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20OpenClaw%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fopenclaw.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-openclaw.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-openclaw.%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-%20A%20private%20dashboard%20that%20chats%20with%20Claude.%20No%20API%20key%20to%20paste.%0A-%20An%20assistant%20that%20stays%20on%20when%20you%20disconnect%20and%20starts%20again%20after%20a%20reboot.%0A-%20Nightly%20backups%20of%20your%20settings%2C%20conversations%2C%20and%20workspace.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20first%2C%20skipping%20VM%20creation%20and%20SSH.%0AThe%20opening%20walkthrough%20is%20for%20the%20owner.%20Telegram%20is%20optional%3A%20don%27t%0Aask%20for%20a%20bot%20token%20during%20initial%20setup.%20Do%20not%20run%20the%20later%20restore%0Aor%20update%20instructions.%0AKeep%20the%20VM%20private.%20Never%20run%20share%20set-public%20or%20disable%20Gateway%20auth.%0AOn%20an%20existing%20VM%2C%20ask%20before%20replacing%20configuration%20or%20a%20service%20on%0Aport%208000.%20Verify%20a%20model%20reply%2C%20Gateway%20health%2C%20enabled%20services%2C%0ALinger%3Dyes%2C%20the%20backup%20timer%2C%20and%20a%20verified%20archive.%20Do%20not%20reboot.%0AGenerate%20the%20browser%20pairing%20link%20last%2C%20after%20the%20owner%20has%20signed%20in%0Ato%20https%3A%2F%2F%3Cvm%3E.exe.xyz%2F.%20Use%20the%20VM%27s%20actual%20hostname.%20Explain%20that%20the%0Alink%20is%20private%2C%20single-use%2C%20and%20expires%20in%20ten%20minutes%3B%20reissue%20on%20request.%0AIf%20the%20owner%20wants%20Telegram%2C%20follow%20%22Connect%20Telegram%20by%20hand%22%2C%20using%0Atheir%20supplied%20token%20instead%20of%20interactive%20read.%20Approve%20only%20the%20code%0Athe%20owner%20confirms%20their%20bot%20sent%20them%2C%20then%20restrict%20access%20to%20their%0Anumeric%20user%20ID.%20Never%20echo%20the%20bot%20token%20back.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/openclaw/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up OpenClaw on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/openclaw.md from top to bottom.\n\nThe recipe's example VM name is my-openclaw. This VM's name is the output of `hostname`: use it wherever the recipe writes my-openclaw. 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- A private dashboard that chats with Claude. No API key to paste.\n- An assistant that stays on when you disconnect and starts again after a reboot.\n- Nightly backups of your settings, conversations, and workspace.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" first, skipping VM creation and SSH.\nThe opening walkthrough is for the owner. Telegram is optional: don't\nask for a bot token during initial setup. Do not run the later restore\nor update instructions.\nKeep the VM private. Never run share set-public or disable Gateway auth.\nOn an existing VM, ask before replacing configuration or a service on\nport 8000. Verify a model reply, Gateway health, enabled services,\nLinger=yes, the backup timer, and a verified archive. Do not reboot.\nGenerate the browser pairing link last, after the owner has signed in\nto https://\u003cvm\u003e.exe.xyz/. Use the VM's actual hostname. Explain that the\nlink is private, single-use, and expires in ten minutes; reissue on request.\nIf the owner wants Telegram, follow \"Connect Telegram by hand\", using\ntheir supplied token instead of interactive read. Approve only the code\nthe owner confirms their bot sent them, then restrict access to their\nnumeric user ID. Never echo the bot token back.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/openclaw/prompt.txt"
  },
  "updated": "2026-10-14",
  "related": [
    "claude-code",
    "code-server",
    "n8n",
    "uptime-kuma"
  ]
}