Telegram Pairing Send Code To Every Start

Quick overview

Modifies OpenClaw's internal pairing logic so unapproved Telegram users receive their pairing code on every /start message, not just the first. The change is a one-line edit in the issuePairingChallenge function, replacing a creation check with a code existence check. Requires restarting the OpenClaw gateway after the edit.

Instead of building a separate code-resend command, this repurposes the existing /start flow so users always have a self-service way to retrieve their code.

Common tasks

• User missed the initial pairing code and needs it resent

• Onboarding users who repeatedly send /start before completing setup

• Debugging pairing flows where the first message was dropped

• Support scenarios where users need to confirm their pairing code

• Environments where Telegram message delivery is unreliable

Install paths

Primary command

openclaw install crazypeace/telegram-pairing-send-code-to-every-start

ClawHub installer

npx clawhub@latest install crazypeace/telegram-pairing-send-code-to-every-start

OpenClaw CLI

openclaw skills install crazypeace/telegram-pairing-send-code-to-every-start

Direct OpenClaw install

openclaw install crazypeace/telegram-pairing-send-code-to-every-start

Skill metadata

• Category: Coding Agents & IDEs

• Language: Markdown

• Version: 1.0.2

• Security status: Suspicious

Review upstream source

The full public SKILL.md body is not directly fetchable for this entry right now, so this page is using the best available catalog metadata. Review the upstream source page for the latest files, version history, and security scan details: https://clawhub.ai/crazypeace/telegram-pairing-send-code-to-every-start