configure

# /telegram:configure — Telegram Channel Setup Writes the bot token to `~/.claude/channels/telegram/.env` and orients the user on access policy. The server reads both files at boot. Arguments passed: `$ARGUMENTS` --- ## Dispatch on arguments ### No args — status and guidance Read both state files and give the user a complete picture: 1. **Token** — check `~/.claude/channels/telegram/.env` for `TELEGRAM_BOT_TOKEN`. Show set/not-set; if set, show first 10 chars masked (`123456789:...`). 2. **Access** — read `~/.claude/channels/telegram/access.json` (missing file = defaults: `dmPolicy: "pairing"`, empty allowlist). Show: - DM policy and what it means in one line - Allowed senders: count, and list display names or IDs - Pending pairings: count, with codes and display names if any 3. **Channel allowlist** — without this, slash commands and the `reply` tool work, but inbound Telegram messages never reach the agent's context. The file is platform-specific: - **macOS**: `/Library/Application Support/ClaudeCode/managed-settings.json` - **Linux**: `/etc/claude-code/managed-settings.json` - **Windows**: `%ProgramData%\ClaudeCode\managed-settings.json` Read the file (it may not exist — that's the common case for standalone plugin installs). Expected shape: ```json { "allowedChannelPlugins": [ {"plugin": "telegram", "marketplace": "5dive-plugins"} ] } ``` Each entry is an **object** `{plugin, marketplace}`...