Skip to content

fix: replace token-like example with obvious placeholder in telegram.md #2788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alex-solovyev merged 1 commit into from
Mar 3, 2026
Merged

fix: replace token-like example with obvious placeholder in telegram.md #2788

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/services/communications/telegram.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ npm install grammy
1. Open Telegram and search for `@BotFather`
2. Send `/newbot` and follow the prompts
3. Choose a name (display name) and username (must end in `bot`)
4. BotFather returns an API token: `123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11`
4. BotFather returns an API token (format: `<bot-id>:<auth-token>`, e.g. `123456789:YOUR-TOKEN-FROM-BOTFATHER`)
5. Store the token securely (see [Security Considerations](#security-considerations))

**BotFather commands**:
Expand Down Expand Up @@ -448,7 +448,7 @@ The proprietary server means there is **no way to independently verify** what ha
gopass insert aidevops/telegram/bot-token

# Or via credentials.sh (600 permissions)
echo 'export TELEGRAM_BOT_TOKEN="123456:ABC..."' >> ~/.config/aidevops/credentials.sh
echo 'export TELEGRAM_BOT_TOKEN="<your-token>"' >> ~/.config/aidevops/credentials.sh

# NEVER commit tokens to git
# NEVER log tokens in output
Expand Down
Loading