Deploy Clawdbot using AcePanel

Technology
,
1

Clawdbot is currently a wildly popular personal AI assistant, so I won’t go into an introduction here. If you’re interested, you can search for it on your own. Let’s jump straight to the practical guide for deploying Clawdbot.

Requirements

  1. Upgrade AcePanel to >= 3.0.3.
  2. Own a domain name (subdomains are acceptable).

First, install the Node.js 24 runtime environment via the panel.

image
image3542×1050 283 KB

After installation, enable pnpm in the panel’s terminal (do not use the panel’s built-in local host; you should either create a new 127.0.0.1 host yourself or use an SSH client, as the panel’s built-in local host does not support full interactivity).

I personally prefer using pnpm, but you can use the default npm if you want.

corepack enable pnpm
pnpm setup
source /root/.bashrc

image
image1332×298 13.2 KB

Once pnpm is installed, you can install clawdbot.

pnpm i clawdbot@latest -g

image
image2614×1350 282 KB

You also need to approve build script execution.

pnpm approve-builds -g

Press the a key to select all, then press Enter and type y to confirm.

image
image2380×500 78.9 KB

Once this is done, you can initialize clawdbot.

clawdbot onboard

image
image1902×1204 148 KB

Agree to the risks, select quick initialization, and I skipped all the settings here just to get it running first.

image
image1358×1114 45.2 KB

You’ll know it’s finished when you see the image below. Copy and save the login URL with the token, as you’ll need it later.

image
image1460×682 29 KB

Don’t rush to start it after installation; modify the configuration file to add the third-party APIs you need.

Configuration file path: /root/.clawdbot/clawdbot.json

Template: OpenAI-compatible Relay

{
  "models": {
    "mode": "merge",
    "providers": {
      "gemini": {
        "baseUrl": "https://your-relay-api/v1",
        "apiKey": "test",
        "api": "openai-completions",
        "models": [
          {
            "id": "gemini-3-flash",
            "name": "gemini-3-flash"
          }
        ]
      }
    }
  }
}

Attached is my configuration reference, which uses the official DeepSeek API. The only thing to note is that when agents reference a model, you need to add the provider prefix, otherwise it will be resolved to the model from Company A.

image
image2784×1702 373 KB

Then install and start the service.

clawdbot daemon install
clawdbot daemon start

image
image1394×500 43.9 KB

After the service starts, since it listens on 127.0.0.1 by default, it cannot be accessed directly. You need to configure a reverse proxy and enable HTTPS.

Go to Panel Apps → Native Apps → Install Nginx/OpenResty, then create a new reverse proxy website and assign your domain name to it.

image
image2142×1046 90.4 KB

Edit the website, go to the HTTPS tab to issue a certificate with one click, then enable HTTPS and HTTP redirection.

image
image962×440 16.5 KB

Append ?token=the token you saved earlier to your domain name, open the backend, and you will be prompted to pair the device.

image
image2472×948 184 KB

Return to the terminal and run clawdbot devices list to view the pending pairing devices.

image
image3022×902 129 KB

Run clawdbot devices approve request-id to approve the pairing.

clawdbot devices approve 98b5fee7-415e-48f3-9e8e-c59886150af9

Then return to the console; when the status changes to OK, you can start using it.

image
image2462×1130 185 KB

Personally, I think this tool is more for fun right now, as none of the commonly used chat apps in China are supported…