You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide/im-bridge/telegram.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,10 +106,11 @@ New chats must be authorized before they can use the bot:
106
106
2. Start a chat with the bot
107
107
3. Send `/subscribe` — the bot replies with a one-time binding key:
108
108
```
109
-
/bind abc123xyz
109
+
abc123xyz
110
110
```
111
111
4.**Authorize the chat** (choose one):
112
-
-**Web chat (recommended):** Copy the `/bind <key>` line and paste it in the CCCC Web chat — the foreman will complete the binding automatically
112
+
-**Web (recommended):** Open **CCCC Web → Settings → IM Bridge**, find it in **Pending Requests**, and click **Approve** (or paste the key in **Bind**)
113
+
-**Foreman-assisted:** If foreman is online, send the key to foreman and ask foreman to bind it
113
114
-**CLI:** Run `cccc im bind --key <key>` on the server
114
115
5. Once authorized, the chat can immediately send and receive messages — no further commands needed
115
116
@@ -174,7 +175,6 @@ Attach files to your message. They're downloaded and stored in CCCC's blob stora
|`/bind <key>`| Authorize this chat using a binding key (paste in CCCC Web chat) |
178
178
|`/unsubscribe`| Stop receiving messages |
179
179
|`/send <message>`| Send to foreman (default) |
180
180
|`/send @<actor> <message>`| Send to a specific agent |
@@ -213,7 +213,7 @@ Your token is invalid. Get a new one from BotFather:
213
213
214
214
### Messages not delivered
215
215
216
-
1. Ensure the chat is authorized (run `/subscribe` → bind the key via Web or CLI)
216
+
1. Ensure the chat is authorized (run `/subscribe` → bind the key via Web, foreman-assisted bind, or CLI)
217
217
2. Check that the CCCC daemon is running
218
218
3. Verify the bridge status in Web UI or via `cccc im status`
219
219
@@ -229,6 +229,6 @@ Telegram has rate limits. If you're sending many messages:
229
229
- Consider enabling 2FA on your Telegram account
230
230
- Review who has access to chats where the bot is subscribed
231
231
- The bot can see all messages in groups where it's added
232
-
-**New chats require key-based authorization** before they can interact with the bot — send `/subscribe` to generate a one-time key, then confirm it from the server side (Web chat or CLI); once bound, the chat is fully authorized
232
+
-**New chats require key-based authorization** before they can interact with the bot — send `/subscribe` to generate a one-time key, then confirm it from the server side (Web Settings > IM Bridge, foreman-assisted bind, or CLI); once bound, the chat is fully authorized
233
233
- Binding keys expire after **10 minutes**; generate a new one with `/subscribe` if it lapses
234
-
- The bind operation must be performed via CCCC Web chat or `cccc im bind --key` on the server — Telegram users cannot self-authorize
234
+
- The bind operation must be performed via CCCC Web Settings (IM Bridge), foreman-assisted bind, or `cccc im bind --key` on the server — Telegram users cannot self-authorize
0 commit comments