Skip to content
TakoAPI
Back to skills

telegram-pairing-send-code-to-every-start

by crazypeace

Coding Agents & IDEs
857Downloads reported by clawskills.sh
1Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message.

Description

What This Skill Does

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.

When to Use It

  • 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

Example Workflow

INPUT

User asks: make unapproved Telegram users see their pairing code every time they send /start

AGENT
  1. 1

    Search /usr/lib/node_modules/openclaw/ for the issuePairingChallenge function

  2. 2

    Locate the line containing if (!created) return { created: false }

  3. 3

    Replace that line with if (!code) return { created: false }

  4. 4

    Back up the original file before saving changes

  5. 5

    Run openclaw gateway restart to apply the modification

OUTPUT

Unapproved users now receive their pairing code on every /start message until they are approved

Installation

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

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links