Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Updated implementation instructions to target the new pairing logic using the async function `issuePairingChallenge(params)`. - The key code change is now to check `if (!code)` instead of `if (!created)`, ensuring a pairing code is sent on every `/start` for unapproved users. - Guidance for finding and modifying the code was updated to match the new structure. - “Some advice” and troubleshooting sections streamlined for current process. - The functionality and purpose remain unchanged: unapproved users receive a pairing code each time they send `/start`.
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
Here's how your AI assistant might use this skill in practice.
User asks: make unapproved Telegram users see their pairing code every time they send /start
- 1Search /usr/lib/node_modules/openclaw/ for the issuePairingChallenge function
- 2Locate the line containing if (!created) return { created: false }
- 3Replace that line with if (!code) return { created: false }
- 4Back up the original file before saving changes
- 5Run openclaw gateway restart to apply the modification
Unapproved users now receive their pairing code on every /start message until they are approved