Telegram integration lets a signed-in Jaidu user link a Telegram account, import plain text into Project Chat, import voice or audio as Project Chat recording cards, make saved text more readable, and receive selected product notifications in Telegram. Project Chat is project-scoped control-plane messaging. It is not host-bound and does not start Codex or workspace execution.

​
Runtime Requirements

Telegram is optional. If TELEGRAM_BOT_TOKEN is missing or empty, the control plane starts without Telegram support. Jaidu supports link tokens in both directions.
1

Start the bot

Open the Telegram bot and send /link.
2

Open the returned link

The bot returns a Jaidu link URL. Open it while signed in to the control plane.
3

Confirm the account

Jaidu redeems the token and attaches the Telegram account to the signed-in user.
Where the web UI exposes Telegram account linking, create a Telegram link token while signed in and open the generated Telegram deep link. The bot redeems the token and links that Telegram account to your Jaidu user.

​
Telegram Import Flow

After linking Telegram:
  1. Send the bot a plain text, voice, or audio message.
  2. For text, the bot saves the message and shows an inline menu for choosing a Project Chat destination.
  3. For voice and audio, the bot downloads the original file, stores it in Jaidu-controlled recording storage, and then shows the same Project Chat destination menu.
  4. Use /send to reopen the most recent saved Telegram message menu.
  5. Use /readable or the inline action to rewrite the most recent saved text into a cleaner readable form. Readable rewriting applies to text messages only.
  6. Send the saved item to Project Chat.
The bot imports Project Chat items as the linked Jaidu user. The linked user must be a project member for the destination project; project read-only users and task-only readers cannot import Telegram messages into Project Chat. Only plain Telegram message.text messages are handled as direct text input. Media captions are not part of this flow. Text imports appear as normal Project Chat text messages. Voice and audio imports appear as normal Project Chat recording cards with an audio artifact and queued transcript processing. Project Chat does not show Telegram usernames, Telegram labels, or bot markers for imported items; source metadata is retained only in backend audit tables.

​
Telegram Notifications

Telegram notifications are a delivery channel for Jaidu product notifications. They use the same product events as the in-app notification feed, then apply the recipient’s account and project preferences before sending a Telegram message. Telegram notification delivery requires all of the following:
  • the control plane is running with TELEGRAM_BOT_TOKEN;
  • your Jaidu account is linked to Telegram;
  • Enable Telegram notifications is on in account settings;
  • the event creates you as an eligible notification recipient;
  • the matching account and project preference is enabled;
  • the action was performed by another user;
  • the event occurs outside your quiet hours.
Project preferences do not add you to an event’s recipient list. For example, enabling Task description changed does not notify a project reader about every issue description edit. You must also be an eligible recipient for that event.

​
Account Defaults

Account settings are the global Telegram gate.

​
Project Defaults

Project notification preferences are per user and per project.

​
Supported Event Matrix

The following events can create Telegram delivery attempts today.

​
Stored But Not Live Yet

These preferences or product ideas are represented in schema/UI but do not send live Telegram notifications yet:
  • project access changed;
  • Project Chat Mentions only;
  • digest delivery;
  • workspace and pull request events.

​
Bot Commands

​
Troubleshooting

Confirm TELEGRAM_BOT_TOKEN, TELEGRAM_BOT_USERNAME, and TELEGRAM_POLLING_ENABLED in the live control-plane process environment. The runtime uses long polling, not a webhook.
Set the call recording storage variables for voice/audio import. Set OPENAI_API_KEY when you also need transcript processing and readable text. The bot can link accounts and import text without OpenAI.
Check TELEGRAM_VOICE_MAX_BYTES. The default limit is 26,214,400 bytes.
Check whether you were an eligible recipient for that event. Normal issue updates go to issue assignees and followers who are organization members, not to every project reader. Project Chat goes to project members and project read-only users who selected All messages, but never to task-only readers or the message author.
Quiet hours skip instant Telegram delivery for the configured account-level time window. They do not queue a digest yet.