Channels let you talk to Kucedr outside the desktop app. A Telegram message arrives, Kucedr runs a background agent turn, and the reply goes back to the originating chat or thread.
| Channel | Status | Notes |
|---|---|---|
| Telegram | Available | Long-polling bot for phone or desktop chat. |
Connect Telegram
- In Settings → Channels, choose the provider and model for channel replies. Optional speech-to-text and text-to-speech model choices are separate.
- Open Telegram and save the bot token.
- Set the direct-message policy and, when needed, direct-sender and group or channel allowlists.
- Send a test message from an allowed sender and check the reply in the same chat or thread.
The current channel detail screen saves credentials and sender policies. It does not expose a runtime enable or disable switch or live connection-status controls.
Shared Behavior
- Direct, group or channel, and thread messages are normalized and routed to the agent.
- Replies target the originating chat, message, and thread where the platform supports it.
- Each channel uses its own configured chat provider and model for replies.
- Long replies are split into platform-sized parts, and delivery receipts distinguish sent, partial, and failed delivery.
/startreturns a fixed connected greeting. Other slash-prefixed channel messages are ignored.- All accepted Telegram messages currently share one fixed bot-session identifier, so channel traffic is not separated per sender.
- Channel runs use the background execution type and an eight-call public-web budget.
Telegram
- Long polling, with pending updates dropped at start.
- Connection, error, and disconnected status events.
- A 60-second health check and exponential reconnect delay from 2 to 60 seconds.
- In-memory duplicate-message protection.
- Replies split at 4,096 characters.
- The runtime supports start, stop, and restart operations; the current detail screen does not expose those controls.
Access Control
Telegram keeps its own enabled state, token, direct-message policy, direct-sender allowlist, group or channel allowlist, and reply model.
- Disabled or tokenless channels reject input, and empty messages are ignored.
- Direct-message policy can be Allowlist (the default), Open, Pairing, or Deny.
- Allowlist mode accepts only configured sender IDs.
- An optional group or channel list restricts which route IDs are accepted.
Partial. Pairing is not usable yet: the policy always rejects with pairing_required, and there is no code-generation or approval flow behind it.
Channel tokens are masked in the interface after saving, but they are stored in ordinary local configuration files. See Privacy And Security.
Channels can send message content and tool inputs to the selected model provider and other connected services. Review the bot's allowed senders before using it for sensitive work.