From 8813c9073b254d54bc4078836f1a6ecd2ae7e72c Mon Sep 17 00:00:00 2001 From: HashWarlock Date: Mon, 26 Jan 2026 19:37:17 -0600 Subject: [PATCH] docs(redpill): add user ID discovery and auto-approval guide Document how to find Telegram and Discord user IDs for pre-approving users. Added comprehensive instructions including: - Environment variables for TELEGRAM_ALLOWED_USERS and DISCORD_ALLOWED_USERS - Step-by-step guide to discover user IDs via pairing messages - Alternative methods (@userinfobot for Telegram, Developer Mode for Discord) - Updated docker-compose and .env examples This completes the auto-approval feature documentation for Phala Cloud deployments, allowing users to skip the manual pairing step. --- docs/providers/redpill.md | 45 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/docs/providers/redpill.md b/docs/providers/redpill.md index a90f81f02..6c536bbd5 100644 --- a/docs/providers/redpill.md +++ b/docs/providers/redpill.md @@ -315,6 +315,9 @@ REDPILL_API_KEY=rp_xxxxxxxxxxxx # Optional: messaging channels (auto-configure on boot) # TELEGRAM_BOT_TOKEN=your-telegram-bot-token # DISCORD_BOT_TOKEN=your-discord-bot-token +# Optional: pre-approve specific users (skips pairing step) +# TELEGRAM_ALLOWED_USERS=123456789,987654321 +# DISCORD_ALLOWED_USERS=123456789012345678,987654321098765432 # Optional: protect the web UI with password auth # GATEWAY_AUTH=password # GATEWAY_PASSWORD=your-secure-password @@ -378,6 +381,8 @@ Access your gateway URL to: | `REDPILL_API_KEY` | Yes | Your Redpill API key (auto-configures all 18 GPU TEE models on first boot) | | `TELEGRAM_BOT_TOKEN` | No | Telegram bot token (auto-configures and starts Telegram channel on boot) | | `DISCORD_BOT_TOKEN` | No | Discord bot token (auto-configures and starts Discord channel on boot) | +| `TELEGRAM_ALLOWED_USERS` | No | Comma-separated Telegram user IDs to pre-approve (e.g. `123456789,987654321`) | +| `DISCORD_ALLOWED_USERS` | No | Comma-separated Discord user IDs to pre-approve (e.g. `123456789012345678,987654321098765432`) | | `GATEWAY_PORT` | No | Gateway port (default: `18789`) | | `GATEWAY_AUTH` | No | Gateway auth mode: `off`, `token`, or `password` (default: `off`) | | `GATEWAY_TOKEN` | No | Gateway token (required when `GATEWAY_AUTH=token`) | @@ -421,6 +426,46 @@ The following channels work in Docker/Linux environments (no Mac services requir Configure channels via the `/setup` wizard at `https://:18789/setup`. +### Finding Your User IDs + +To pre-approve users (skip pairing), you need their platform-specific user IDs: + +**Telegram User ID:** +1. Send a message to your bot on Telegram +2. The bot will reply with a pairing code and show your user ID: + ``` + Clawdbot: access not configured. + + Your Telegram user id: 1868695838 + + Pairing code: ABCD1234 + ``` +3. Copy the user ID (e.g., `1868695838`) +4. Add it to `.env`: `TELEGRAM_ALLOWED_USERS=1868695838` + +**Discord User ID:** +1. Send a message to your bot on Discord +2. The bot will reply with a pairing code and show your user ID: + ``` + Clawdbot: access not configured. + + Your Discord user id: 723570216251949194 + + Pairing code: XYZW5678 + ``` +3. Copy the user ID (e.g., `723570216251949194`) +4. Add it to `.env`: `DISCORD_ALLOWED_USERS=723570216251949194` + +**Alternative Methods:** + +Telegram: +- Use [@userinfobot](https://t.me/userinfobot) on Telegram +- Forward a message to the bot to get the sender's ID + +Discord: +- Enable Developer Mode: Settings → Advanced → Developer Mode +- Right-click your username → Copy User ID + ### Persistent Storage The `clawdbot-data` volume stores: