Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
此技能描述如何修改 OpenClaw 的 Telegram 配对逻辑,使未批准的用户在配对被批准前,每次发送 /start 消息时都能收到配对码回复。
需要让未批准的用户每次发送 /start 都收到配对消息(而非仅首次) 用户可能错过首次配对消息,需要重新获取配对码 提升用户体验,确保用户始终能获得配对指引
在你正在运行的代码中搜索下面的代码段 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")) }); }
将条件判断从 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")) }); }
修改完成后需要重启 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) 如需回滚,请使用备份文件替换修改后的文件
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.