Skip to content

feat: support multiple Telegram allowlisted users - #22

Open
musichen wants to merge 1 commit into
badlogic:mainfrom
musichen:feat/multiple-telegram-allowlist
Open

feat: support multiple Telegram allowlisted users#22
musichen wants to merge 1 commit into
badlogic:mainfrom
musichen:feat/multiple-telegram-allowlist

Conversation

@musichen

Copy link
Copy Markdown

Summary

Allow the Telegram bridge to authorize multiple Telegram accounts while keeping existing single-account configurations working.

What changed

  • Add allowedUserIds as the canonical allowlist setting.
  • Accept messages from any user ID in the list.
  • Migrate the existing allowedUserId setting to allowedUserIds when the configuration is read.
  • Update pairing, status reporting, and documentation for multiple accounts.

Configuration

"allowedUserIds": [530236679, 123456789]

Existing configurations using allowedUserId are migrated automatically.

Testing

Verified the TypeScript changes by inspection and validated the JSON configuration format.

@musichen

musichen commented Aug 15, 2026

Copy link
Copy Markdown
Author

@badlogic
One compatibility note: existing configurations using the single-user setting

"allowedUserId": 530236679

continue to work. On the next bridge reconnect, the setting is migrated automatically to:

"allowedUserIds": [530236679]

This preserves the existing authorized account while allowing additional IDs to be added.

xqicxx pushed a commit to xqicxx/pi-telegram that referenced this pull request Aug 26, 2026
…n-only contract (separate message removed); add sendTranscript to config type; final type hygiene
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant