Skill: 总是响应未配对用户的 /start 消息 | Always respond to /start messages from unpaired users

Owner: crazypeace

Summary: Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message before approval. Use when users need to repeatedly access pairing codes after the initial request, ensuring consistent access to pairing instructions even if the initial code was missed or lost.

Tags: latest:1.0.4

Version history:

v1.0.4 | 2026-02-08T04:02:52.736Z | user

• Removed the automation script apply-pairing-fix.sh; step-by-step manual modification is now required.
• Updated instructions to guide users in manually locating and editing the relevant code block for Telegram pairing.
• Provided practical tips for searching file locations and verifying the code change.
• No changes to underlying pairing logic; usage remains the same.

v1.0.3 | 2026-02-03T04:11:13.803Z | user

Version 1.0.3

• No file changes detected in this release.
• Documentation and usage instructions remain consistent with the previous version.
• No new features, fixes, or adjustments added.

v1.0.2 | 2026-02-03T03:32:26.579Z | user

Version 1.0.2

• Added apply-pairing-fix.sh script to automate patching of Telegram pairing message logic.
• Now provides an automated method (via script) in addition to manual steps for modifying OpenClaw, making updates easier and safer.
• Documentation updated to include script usage and clearer instructions for both automated and manual application.
• Emphasizes backup, service restart, and verification processes.

v1.0.1 | 2026-02-03T02:22:52.636Z | auto

• 修改配对逻辑，判断条件由 if (created) 改为 if (code)，确保存在有效配对码时总是发送配对消息。
• 未批准用户每次发送 /start 都能收到当前配对码回复（无论是否首次申请）。
• 增加逻辑解释，说明 upsertTelegramPairingRequest 的返回字段以及改动原因。
• 其余文档内容与原说明保持一致。

v1.0.0 | 2026-02-02T15:44:39.502Z | user

• Users now receive the Telegram pairing code every time they send /start before approval, not just the first time.
• Modified the pairing message logic by removing the if (created) condition, ensuring the pairing message always sends.
• No changes to underlying pairing code generation; only message delivery behavior is affected.
• Remember to restart OpenClaw for the changes to take effect.

Archive index:

Archive v1.0.4: 2 files, 2076 bytes

Files: SKILL.md (3924b), _meta.json (149b)

File v1.0.4:SKILL.md

---

name: telegram-pairing-customization description: Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message before approval. Use when users need to repeatedly access pairing codes after the initial request, ensuring consistent access to pairing instructions even if the initial code was missed or lost.

Telegram 配对消息持续响应技能

概述

此技能描述如何修改 OpenClaw 的 Telegram 配对逻辑，使未批准的用户在配对被批准前，每次发送 /start 消息时都能收到配对码回复。

何时使用此技能

• 需要让未批准的用户每次发送 /start 都收到配对消息（而非仅首次）
• 用户可能错过首次配对消息，需要重新获取配对码
• 提升用户体验，确保用户始终能获得配对指引

执行步骤

1. 找到需要修改的文件

在你正在运行的代码中搜索下面的代码段

if (created) {
  logger.info({
    chatId: candidate,
    username: from?.username,
    firstName: from?.first_name,
    lastName: from?.last_name,
    matchKey: allowMatch.matchKey ?? "none",
    matchSource: allowMatch.matchSource ?? "none"
  }, "telegram pairing request");
  await withTelegramApiErrorLogging({
    operation: "sendMessage",
    fn: () => bot.api.sendMessage(chatId, [
      "OpenClaw: access not configured.",
      "",
      `Your Telegram user id: ${telegramUserId}`,
      "",
      `Pairing code: ${code}`,
      "",
      "Ask the bot owner to approve with:",
      formatCliCommand("openclaw pairing approve telegram <code>")
    ].join("\n"))
  });
}

2. 实施修改

将条件判断从 if (created) 修改为 if (code):

if (do) { // <-- 关键修改点
  logger.info({
    chatId: candidate,
    username: from?.username,
    firstName: from?.first_name,
    lastName: from?.last_name,
    matchKey: allowMatch.matchKey ?? "none",
    matchSource: allowMatch.matchSource ?? "none"
  }, "telegram pairing request");
  await withTelegramApiErrorLogging({
    operation: "sendMessage",
    fn: () => bot.api.sendMessage(chatId, [
      "OpenClaw: access not configured.",
      "",
      `Your Telegram user id: ${telegramUserId}`,
      "",
      `Pairing code: ${code}`,
      "",
      "Ask the bot owner to approve with:",
      formatCliCommand("openclaw pairing approve telegram <code>")
    ].join("\n"))
  });
}

3. 重启服务

修改完成后需要重启 OpenClaw 服务以使更改生效:

openclaw gateway restart

一些建议

在寻找需要修改的文件时, 建议先搜索 Ask the bot owner to approve with: 可以帮助你先大幅缩小处理范围, 过滤出最有可能的几个文件.

一个建议的起始目录为 /usr/lib/node_modules/openclaw/

工作原理

• upsertTelegramPairingRequest 函数返回 {code, created} 对象
• 当用户首次请求配对时：created: true，有配对码
• 当用户再次请求配对时：created: false，但仍有相同的配对码（只要配对请求未过期或未被批准）
• 通过检查 if (code) 而不是 if (created)，确保用户每次请求都能收到有效的配对码

验证修改

• 让未配对的用户发送 /start 命令
• 确认用户收到配对码消息
• 再次发送 /start 命令，确认用户再次收到相同的配对码

注意事项

• 修改系统文件前务必备份原始文件
• 修改后的文件在 OpenClaw 更新时可能会被覆盖，需要重新应用修改
• 需要适当的文件系统权限来修改 OpenClaw 的安装文件
• 修改后应测试以确保功能正常

故障排除

• 如果修改不生效，请确认是否正确重启了 OpenClaw 服务
• 如果找不到文件路径，请确认 OpenClaw 的实际安装路径
• 如果权限不足，请使用适当的权限提升方法（如 sudo）
• 如需回滚，请使用备份文件替换修改后的文件

File v1.0.4:_meta.json

{ "ownerId": "kn769hxajq747rnm1pyf9zmtns80cn81", "slug": "telegram-pairing-customization", "version": "1.0.4", "publishedAt": 1770523372736 }

Archive v1.0.3: 3 files, 3337 bytes

Files: scripts/apply-pairing-fix.sh (1632b), SKILL.md (6044b), _meta.json (149b)

File v1.0.3:SKILL.md

---

name: telegram-pairing-customization description: Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message before approval. Use when users need to repeatedly access pairing codes after the initial request, ensuring consistent access to pairing instructions even if the initial code was missed or lost.

Telegram 配对消息持续响应技能

概述

此技能描述如何修改 OpenClaw 的 Telegram 配对逻辑，使未批准的用户在配对被批准前，每次发送 /start 消息时都能收到配对码回复。

何时使用此技能

• 需要让未批准的用户每次发送 /start 都收到配对消息（而非仅首次）
• 用户可能错过首次配对消息，需要重新获取配对码
• 提升用户体验，确保用户始终能获得配对指引

执行步骤

方法 1: 使用自动化脚本（推荐）

运行提供的脚本来自动执行修改：

bash /root/.openclaw/workspace/skills/telegram-pairing-customization/scripts/apply-pairing-fix.sh

脚本将自动完成以下操作：

• 备份原始文件
• 修改条件判断从 if (created) 为 if (code)
• 显示操作摘要

方法 2: 手动修改

如果需要手动修改，请按以下步骤操作：

1. 备份原始文件

在进行任何修改之前，备份原始文件：

cp /usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js /usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js.backup

2. 修改配对消息触发逻辑

文件路径：/usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js

找到以下原始代码段：

if (dmPolicy === "pairing") {
    try {
        const from = msg.from;
        const telegramUserId = from?.id ? String(from.id) : candidate;
        const { code, created } = await upsertTelegramPairingRequest({
            chatId: candidate,
            username: from?.username,
            firstName: from?.first_name,
            lastName: from?.last_name,
        });
        if (created) {  // <-- 关键修改点
            logger.info({
                chatId: candidate,
                username: from?.username,
                firstName: from?.first_name,
                lastName: from?.last_name,
                matchKey: allowMatch.matchKey ?? "none",
                matchSource: allowMatch.matchSource ?? "none",
            }, "telegram pairing request");
            await withTelegramApiErrorLogging({
                operation: "sendMessage",
                fn: () => bot.api.sendMessage(chatId, [
                    "OpenClaw: access not configured.",
                    "",
                    `Your Telegram user id: ${telegramUserId}`,
                    "",
                    `Pairing code: ${code}`,
                    "",
                    "Ask the bot owner to approve with:",
                    formatCliCommand("openclaw pairing approve telegram <code>"),
                ].join("\n")),
            });
        }
    }
    catch (err) {
        logVerbose(`telegram pairing reply failed for chat ${chatId}: ${String(err)}`);
    }
}

将条件判断从 if (created) 修改为 if (code)：

if (dmPolicy === "pairing") {
    try {
        const from = msg.from;
        const telegramUserId = from?.id ? String(from.id) : candidate;
        const { code, created } = await upsertTelegramPairingRequest({
            chatId: candidate,
            username: from?.username,
            firstName: from?.first_name,
            lastName: from?.last_name,
        });
        if (code) {  // Send pairing message if we have a valid code (either newly created or previously created)
            logger.info({
                chatId: candidate,
                username: from?.username,
                firstName: from?.first_name,
                lastName: from?.last_name,
                matchKey: allowMatch.matchKey ?? "none",
                matchSource: allowMatch.matchSource ?? "none",
            }, "telegram pairing request");
            await withTelegramApiErrorLogging({
                operation: "sendMessage",
                fn: () => bot.api.sendMessage(chatId, [
                    "OpenClaw: access not configured.",
                    "",
                    `Your Telegram user id: ${telegramUserId}`,
                    "",
                    `Pairing code: ${code}`,
                    "",
                    "Ask the bot owner to approve with:",
                    formatCliCommand("openclaw pairing approve telegram <code>"),
                ].join("\n")),
            });
        }
    }
    catch (err) {
        logVerbose(`telegram pairing reply failed for chat ${chatId}: ${String(err)}`);
    }
}

3. 重启服务

修改完成后需要重启 OpenClaw 服务以使更改生效：

openclaw gateway restart

工作原理

• upsertTelegramPairingRequest 函数返回 {code, created} 对象
• 当用户首次请求配对时：created: true，有配对码
• 当用户再次请求配对时：created: false，但仍有相同的配对码（只要配对请求未过期或未被批准）
• 通过检查 if (code) 而不是 if (created)，确保用户每次请求都能收到有效的配对码

验证修改

• 让未配对的用户发送 /start 命令
• 确认用户收到配对码消息
• 再次发送 /start 命令，确认用户再次收到相同的配对码

注意事项

• 修改系统文件前务必备份原始文件
• 修改后的文件在 OpenClaw 更新时可能会被覆盖，需要重新应用修改
• 需要适当的文件系统权限来修改 OpenClaw 的安装文件
• 修改后应测试以确保功能正常

故障排除

• 如果修改不生效，请确认是否正确重启了 OpenClaw 服务
• 如果找不到文件路径，请确认 OpenClaw 的实际安装路径
• 如果权限不足，请使用适当的权限提升方法（如 sudo）
• 如需回滚，请使用备份文件替换修改后的文件

File v1.0.3:_meta.json

{ "ownerId": "kn769hxajq747rnm1pyf9zmtns80cn81", "slug": "telegram-pairing-customization", "version": "1.0.3", "publishedAt": 1770091873803 }