{"id":49367,"date":"2026-01-28T15:28:03","date_gmt":"2026-01-28T07:28:03","guid":{"rendered":"https:\/\/www.1ai.net\/?p=49367"},"modified":"2026-01-28T15:28:03","modified_gmt":"2026-01-28T07:28:03","slug":"clawdbot%e6%80%8e%e4%b9%88%e7%94%a8%ef%bc%9f%e4%b8%80%e5%a4%9c%e7%88%86%e7%81%ab%e7%9a%84clawdbot%e8%af%a6%e7%bb%86%e9%85%8d%e7%bd%ae%e6%95%99%e7%a8%8b","status":"publish","type":"post","link":"https:\/\/www.1ai.net\/en\/49367.html","title":{"rendered":"How does Clawdbot work? Clawdbot detailed configuration course for one night of fire"},"content":{"rendered":"

Clawdbot<\/a> One night of fire\u3002<\/p>\n

Yesterday, this Clawdbot was on several platforms, and as an open-source project, GitHub's Stars surged by more than 9000 in one day, adding over 200 PRs overnight, and the founders themselves said it blew up, and it was crazy\u3002<\/p>\n

In short, Clawdbot is a personal AI assistant, fully localized, working on Claude for 7 hours\u3002<\/p>\n

Why is it on fire<\/strong><\/p>\n

NOT BECAUSE 7*24 HOURS, NOT BECAUSE IT CAN ACCESS FILES, BROWSERS, E-MAILS, BUT BECAUSE THIS THING SUPPORTS YOUR INTERACTION ON THE APP\u3002<\/p>\n

For example, you're playing a game and you're putting him on an iMessage mission, and it's dry, and when you get back, you're done. The whole process was like sending a message to a friend in a tweet\u3002<\/p>\n

Support for almost all mainstream communication platforms: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, Microsoft Teams, Matrix, Zalo, WebChat\u3002<\/p>\n

Second: it runs on your own equipment, Mac, PC, strawberry pie, cloud servers\u3002<\/p>\n

This point is also timely, and now AI bot is largely in the browser, and of course there is also a desktop end, such as Minimax, which introduced desktop-end APPs at the previous time, to operate the browser itself, and Claude Cowork to access local folder operations files\u3002<\/p>\n

But Clawdbot can be deployed in any terminal device, computers, watches, berry pies, even smart glasses, like, imagine that the space just opened\u3002<\/p>\n

However, if you deploy the equipment, it has to be on-line\u3002<\/p>\n

It's just a server application, the core of the Clawdbot architecture is Gateway, the brain of the entire system, the only central node through which all the messages go. If it's offline, the whole system is paralysed\u3002<\/p>\n

Because it's on the line, it's able to contact you on its own, send the weather, the agenda, the news, the mission schedule, and become an active assistant, unlike passive chat robots. If you just have to answer passively, you can use ChatGPT\u3002<\/p>\n

The Clawdbot fire also triggered a rush by Mac Mini, but it was not necessary at all, because I thought it would be most convenient to deploy on a cloud server, and I recommended it most\u3002<\/p>\n

Because it has access to your local equipment, and although I have not yet figured out how it was obtained, it is a very big one, and it is not deployed on your laptop to protect your local documents\u3002<\/p>\n

And your computer couldn't have been there 24 hours before it shut down. So choosing a cloud server is the best that can run for 24 hours\u3002<\/p>\n

I spent 30 bucks renting a VPS, Mac Mini the cheapest $599 (about $4300), a VPS 30 a month and 10 years to $3,600. And the VPS is broken and re-opened\u3002<\/p>\n

I see a lot of people who can't handle this. A lot of people are stuck in the deployment\u3002<\/p>\n

So this article, I put the deployment course at the topHands on your hands and hands from zero to working, so white can read\u3002<\/strong><\/p>\n

Directly deploy from zero to service only 7 steps<\/p>\n

Friends of Claude Code<\/strong>:<\/p>\n

If you think the manual configuration is too complicated, I'm readySkill<\/strong>It's smart enough to fit your configuration. It's automatic\u3002<\/p>\n

However, I would suggest that we take a look at the curriculum and understand the rationale for deployment. We'll find out how\u3002<\/p>\n

Manual deployment: You need three things<\/p>\n

\"685ced17j00t9kb04000ld000iw002p\"<\/p>\n

First step: Buying a cloud server (10 minutes)<\/strong><\/p>\n

For example: Ariyun\/Ting Clouds\/Wan Yun\/Nonameless Cloud Server<\/strong>Freshman friendly\u3002<\/p>\n

    \n
  1. open https:\/\/www.aliyun.com\/product\/swas (for example only, every cloud server)<\/li>\n
  2. Registered login (cell phone number only)<\/li>\n
  3. Select Configuration:<\/li>\n<\/ol>\n

    Geographical<\/strong>: Hong Kong (complex domestic filing required, not required in Hong Kong)<\/p>\n

    Mirror<\/strong>:Ubuntu 22.04 LTS<\/p>\n

    Package<\/strong>: 2 NUCLEAR 2G, 30GB SSD<\/p>\n

    length of time<\/strong>: Buy first 1 month<\/p>\n

    Pay complete, access console, open port\u3002<\/p>\n

    Reset Password<\/strong>and set for themselves a good note\u3002<\/p>\n

    Write down three messages<\/strong>:<\/p>\n

    IP address: xxxx.xxx.xxxxx
    \nuser name: root
    \npassword: xxx<\/p>\n

    \n
      \n
    • This server is the Lobster's Home, and it's going to run around here for seven times 24 hours\u3002<\/li>\n<\/ul>\n<\/blockquote>\n

      Step 2: Create Telegram robot (5 minutes)<\/strong><\/p>\n

      It can be done on the phone without a server\u3002This is the entrance to your interaction with Clawdbot\u3002<\/strong><\/p>\n

      Procedure<\/strong>:<\/p>\n

      Open Telegram, search @BotFather<\/p>\n

      2. Click\u00a0START<\/strong>, send the command:<\/p>\n

      \/newbot<\/p>\n

      This step is to create a robot, BotFather, which will give you a name for the robot, just knock on the \"qq robot.\" (Can be Chinese, similar nicknames)<\/p>\n

      \"f22989c8j00t9kb0t0018d000lp00bhp\"<\/p>\n

      Then you take a user name, MadscBot. Username similar to QQQ, cannot be repeated\u3002<\/p>\n

      After success<\/strong>BotFather will send you a token\u3002<\/p>\n

      \"68c53971j00t9kb19002800m800e1p\"<\/p>\n

      4. copy token, save<\/strong>i don't know. this token, it's important because it's going to be givenClawdbot<\/strong>Clawdbot connects to this bot\u3002<\/p>\n

      5. Click t.me\/McdscBot to add a robot friend in advance\u3002<\/p>\n

      Step 3: Get Claude API Key (5 minutes)<\/strong><\/p>\n

      THERE ARE TWO OPTIONS FOR RECOMMENDING THIRD-PARTY API TO DOMESTIC USERS\u3002<\/p>\n

      Option A: Triangular Transit to Support Claude Model API<\/strong><\/p>\n

        \n
      • Cell phone registration, payment for treasure\/micro-credit<\/li>\n
      • It's worth 50 bucks for a long time<\/li>\n
      • Create API Key, Copy Save<\/li>\n
      • format: sk-xxxxxxxxxxxxxxxxxxxxxxxxxx<\/li>\n<\/ul>\n

        Program B: Official Anthropic API<\/strong><\/p>\n

          \n
        • visit https:\/\/console.antropic.com<\/li>\n
        • Need a phone number from abroad<\/li>\n
        • Based on volume, approximately $15\/million tokens<\/li>\n<\/ul>\n

          Take your API Key<\/strong>The next step is to use\u3002<\/p>\n

          (10,000 words omitted here)<\/p>\n

          Step 4: Login server (3 minutes)<\/strong><\/p>\n

          Landing the first purchase of the cloud server\u3002<\/p>\n

          Windows Users<\/strong>:<\/p>\n

          1. Press Win+R, enter cmd, return the car
          \n2. Enter: ssh root@your server IP
          \n3. Enter password (do not show, paste the vehicle directly)
          \nSeeing root@xxxx: ~# is connected<\/p>\n

          Mac\/ Linux User<\/strong>:<\/p>\n

          1. Opening of terminals
          \n2. Enter: ssh root@your server IP
          \n3. Enter password<\/p>\n

          Step 5: Installation of Clawdbot (10 minutes)<\/strong><\/p>\n

          Link to the server and copy the paste to execute the following command:<\/p>\n

          _# 1. Update_apt_
          \ni don't know what you're talking about
          \n_# 2. First key install Clawdbot_
          \ncurl-fsSL https:\/\/clawd.bot\/install.sh bash
          \n_# 3. \u7b49\u5f85\u5b89\u88c5\u5b8c\u6210\uff0c\u770b\u5230 “Installation complete!” \u5c31\u6210\u529f\u4e86_<\/p>\n

          Re-execut 2 steps if error is reported\u3002<\/p>\n

          Step 6: Configure Clawdbot<\/strong><\/p>\n

          It's the easiest step to make a mistake, working with me\u3002<\/p>\n

            \n
          1. edit profile: nano \/ root\/.clawdbot\/clawdbot.json<\/li>\n
          2. Delete all content: Delete the original text by Ctrl+K line until the document is completely blank\u3002<\/li>\n
          3. Modify configuration: Copy the following code as it is\u3002<\/li>\n<\/ol>\n

            IF YOU'RE USING A THIRD PARTY, API<\/strong>, copy this:<\/p>\n

            {“models”: {“providers”: {“xxx”: {“baseUrl”:\u00a0“https:\/\/xxx.xx”,”apiKey”:\u00a0“\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684API Key”,”api”:\u00a0“anthropic-messages”,”models”: [{“id”:\u00a0“claude-opus-4-5-20251101″,”name”:\u00a0“Claude Opus 4.5″,”reasoning”:\u00a0true,”input”: [“text”,\u00a0“image”],”contextWindow”:\u00a0200000,”maxTokens”:\u00a04096}]}}},”channels”: {“telegram”: {“enabled”:\u00a0true,”botToken”:\u00a0“\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684Bot Token”,”profiles”: [“default”]}},”agents”: {“defaults”: {“model”: {“primary”:\u00a0“xxxx\/claude-opus-4-5-20251101”}}}}<\/p>\n

            If you're using official Anthropic API<\/strong>, copy this:<\/p>\n

            {“models”: {“providers”: {“anthropic”: {“apiKey”:\u00a0“\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684Anthropic API Key”}}},”channels”: {“telegram”: {“enabled”:\u00a0true,”botToken”:\u00a0“\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684Bot Token”,”profiles”: [“default”]}},”agents”: {“defaults”: {“model”: {“primary”:\u00a0“anthropic\/claude-opus-4-5-20251101”}}}}<\/p>\n

            And then we change three places\u3002<\/p>\n

              \n
            • \u628a\u00a0“apiKey”: “\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684API Key”\u00a0\u7684\u5f15\u53f7\u91cc\u5185\u5bb9\u6362\u6210\u4f60\u7684 API Key<\/li>\n
            • \u628a”https\/\/xxx.xx”: “\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u81ea\u5df1\u7684”\u00a0\u7684\u5f15\u53f7\u91cc\u5185\u5bb9\u6362\u6210\u4f60\u7684\u4e2d\u8f6c\u7ad9 Base URL<\/li>\n
            • \u628a”botToken”: “\u5728\u8fd9\u91cc\u7c98\u8d34\u4f60\u7684Bot Token”\u7684\u5f15\u53f7\u91cc\u5185\u5bb9\u6362\u6210\u4f60\u7684 Bot Token\uff08\u5c31\u662f\u7b2c\u4e8c\u6b65\u91cc telegram \u7684 bot token\uff09<\/li>\n<\/ul>\n

              Save exit:<\/strong><\/p>\n

                \n
              • Press Ctrl+O to save (indicate file name, go straight back)<\/li>\n
              • Press Ctrl+X to exit<\/li>\n<\/ul>\n

                Step 7: Start service (5 minutes)<\/strong><\/p>\n

                _# 1. ENABLE DURABILITY (TO KEEP SERVICES RUNNING) _
                \nthis post is part of our special coverage global voices 2011<\/p>\n

                _#2. Set up the environment variable_export XDG_RUNTIME_DIR=\/run\/user\/0<\/p>\n

                _# 3. START-UP SERVICES_
                \nsystemctl –user start clawdbot-gateway.service<\/p>\n

                _#4 CHECK STATUS_
                \nsystemctl –user status clawdbot-gateway.service<\/p>\n

                It's working<\/strong><\/p>\n

                If you see a red error, execute this view log:<\/p>\n

                journalctl –user -u clawdbot-gateway.service -n 30 –no-pager<\/p>\n

                Step 8: Match your Telegram account (3 minutes)<\/strong><\/p>\n

                  \n
                1. Open Telegram, find your robot<\/li>\n
                2. Send any message, like, hello<\/li>\n
                3. Robot response:<\/li>\n<\/ol>\n

                  \"72b74585j00t9kb2i0018d000m00ffp\"<\/p>\n

                  4. Copy pairing<\/p>\n

                  RETURN TO SERVER SSH WINDOW TO EXECUTE:<\/p>\n

                  i'm not sure I'm going to do this<\/p>\n

                  6 (REPLACE ABC 123 WITH YOUR PAIR)<\/p>\n

                  Go back to Telegram and send another hi<\/p>\n

                  If the robot returns, congratulations on the successful deployment! Zenium<\/strong><\/p>\n

                  \"e26d59b4j00t9kb2t0028d000ly00i1p\"<\/p>\n

                  III. The easiest pit to step on<\/strong><\/p>\n

                  When I deployed, I stepped on three major pits and shared them with you. Many people are stuck in these places\u3002<\/p>\n

                  TUNNEL 1: THIRD PARTY API CONFIGURATION POSITION<\/p>\n

                  The third party Claude API's configuration has two hidden rulesIt's not in the official file<\/strong>I tried all night to find out:<\/p>\n

                  Example of error<\/strong>:<\/p>\n

                  “api”:\u00a0“anthropic”, \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u274c \u9519\uff01\u5f88\u591a\u4eba\u5199\u6210\u8fd9\u4e2a
                  \n“baseUrl”:\u00a0“https:\/\/xxx.xx\/v1”\u00a0 \u274c \u9519\uff01\u591a\u4e86\/v1<\/p>\n

                  Correct Example<\/strong>:<\/p>\n

                  “api”:\u00a0“anthropic-messages”, \u00a0\u2705 \u5bf9\uff01\u5fc5\u987b\u8fd9\u6837\u5199
                  \n“baseUrl”:\u00a0“https:\/\/xxx.xx”\u00a0 \u00a0 \u00a0\u2705 \u5bf9\uff01\u4e0d\u8981\u5e26\/v1<\/p>\n

                  Pocket 2: Reconfiguration must be cleared<\/p>\n

                  This pit stuck me for half an hour. After each change of profile, the cache must be cleaned and restarted, otherwise the new configuration is not effective:<\/p>\n

                  _# Cleanup Cache_rm-ref \/ root\/.clawdbot\/agendas\/main\/agent\/sessions\/*
                  \n_# Restart Service_export XDG_RUNTIME_DIR=\/run\/user\/0
                  \nsystemctl –user restart clawdbot-gateway.service<\/p>\n

                  Symptom<\/strong>: THE OLD MODEL\/API IS SHOWN IN THE LOG EVEN THOUGH THE CONFIGURATION HAS BEEN CHANGED. YOU SUSPECT THAT THE CONFIGURATION ISN'T WORKING, IT'S CHANGING OVER AND OVER AND OVER AGAIN\u3002<\/p>\n

                  reason<\/strong>: Clawdbot Caches session status, including model configuration, API connection, etc. Undefined cache, it continues with old ones\u3002<\/p>\n

                  Pocket 3: Services restarted (most difficult)<\/p>\n

                  If you find that the service is automatically restarted every 10-15 seconds, there is an error in the log, usually because:<\/p>\n

                    \n
                  1. Linger is not enabled<\/strong>\u00a0– SSH \u65ad\u5f00\u540e\u670d\u52a1\u88ab\u6740\u6b7b<\/li>\n
                  2. Session cache damage<\/strong>\u00a0– \u65e7\u7684 session \u6587\u4ef6\u5bfc\u81f4\u542f\u52a8\u5931\u8d25<\/li>\n<\/ol>\n

                    Full Solutions<\/strong>:<\/p>\n

                    _# 1. Enable linger (to keep services running)_
                    \nthis post is part of our special coverage global voices 2011
                    \nloginctl show-user root | root Linger _ # confirms Linger=yes#2. Cleanup session cache_rm-ref \/ root\/.clawdbot\/agendas\/main\/agent\/sessions\/*<\/p>\n

                    _# 3. Restart Service_export XDG_RUNTIME_DIR=\/run\/user\/0
                    \nsystemctl –user restart clawdbot-gateway.service<\/p>\n

                    _#4 MONITOR LOG CONFIRMING THAT IT WILL NOT BE RESTARTED
                    \njournalctl –user -u clawdbot-gateway.service -f<\/p>\n

                    Why is Linger so important<\/strong><\/p>\n

                    Because Clawdbot uses the User Level System service, the service will stop by default after the user logs out (SSH disconnect). When Linger is enabled, the service becomes \"continuing\" even if you turn off the terminal\u3002<\/p>\n

                    Remember that, there's a lot less detour\u3002<\/p>\n

                    iv. Results: What can it do<\/strong><\/p>\n

                    After the deployment was completed, I made it fit my skill in Telegram\u3002<\/p>\n

                    \"5b258570j00t9kb3g003ld000u000upp\"<\/p>\n

                    And then, to Bot, he said, \"Take a look at today's choice.\" Three seconds later, it spits out a full list of questions, including today ' s AI Technology Hotspot Top 5, and each news item shows a value rating and a suitable type of article, clearly and clearly\u3002<\/p>\n

                    Just like Claude Code, it was done in Telegram. I also tested the document to make it a table of 10 dissertations, which automatically resolves the document to extract key information to generate structured tables\u3002<\/p>\n

                    \u751a\u81f3\u53ef\u4ee5\u8ba9\u5b83\u5199\u4e2a Python \u811a\u672c\uff0c\u6bcf\u5929\u65e9\u4e0a 8 \u70b9\u6293\u53d6 Hacker News \u524d 10 \u6761\u53d1\u7ed9\u6211\u3002\u5982\u679c\u4f60\u7528\u7684\u662f Mac\uff0c\u5b83\u8fd8\u80fd\u63a7\u5236\u6d4f\u89c8\u5668\u81ea\u52a8\u767b\u5f55\u7f51\u7ad9\u3001\u586b\u5199\u8868\u5355\u3001\u6279\u91cf\u4e0b\u8f7d\u6587\u4ef6…<\/p>\n

                    Anyway, Claude Code can do what he can, but the difference is that you send a message on the phone and it works on the server\u3002<\/p>","protected":false},"excerpt":{"rendered":"

                    Clawdbot one night fire. Yesterday, this Clawdbot was on several platforms, and as an open-source project, GitHub's Stars surged by more than 9000 in one day, adding over 200 PRs overnight, and the founders themselves said it blew up, and it was crazy. In short, Clawdbot is a personal AI assistant, fully localized, working on Claude for 7 hours. Why is it on fire? Not because 7*24 hours, not because it can access files, browsers, e-mails, but because this thing supports your interaction on the APP. For example, you're playing a game at iMessag<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[149,144],"tags":[8211,8219,2894],"collection":[],"class_list":["post-49367","post","type-post","status-publish","format-standard","hentry","category-jiaocheng","category-baike","tag-clawdbot","tag-2894"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts\/49367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/comments?post=49367"}],"version-history":[{"count":0,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/posts\/49367\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/media?parent=49367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/categories?post=49367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/tags?post=49367"},{"taxonomy":"collection","embeddable":true,"href":"https:\/\/www.1ai.net\/en\/wp-json\/wp\/v2\/collection?post=49367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}