Telegram for Codex

Keep coding. Stay in the loop.

Bring requested task updates, questions and selected files from Codex to your connected Telegram chat. Reply to a question with a tap, then let Codex pick up the answer — without resending the question.

Русский · Connection setup · License

A configured backend is required. This is the open-source client plugin, not a hosted Telegram service or a bot server. The bundled MCP URL is the canonical Bears endpoint; public self-service onboarding is not available. Installing this repository alone does not create an account, connect a bot, or provide working credentials. Use an existing authorized compatible deployment.

Ask naturally

You ask	The plugin helps Codex
“Let me know in Telegram when this is done.”	Send a short, truthful task report — not the full transcript.
“Ask me which option to use.”	Send a question with buttons and retrieve the matching reply.
“Keep me posted if you get blocked.”	Notify you about a meaningful blocker, without noisy heartbeats.
“Send this report to Telegram.”	Stream the file you selected without passing its contents through the model.

Five focused skills cover conversation, task updates, file transfer, bot UI design and bot-to-bot testing. The original 40 scenarios and new bot-specific guidance load only when needed.

Install

With a current Codex CLI that supports plugins:

codex plugin marketplace add BearsCLOUD/telegram-for-codex
codex plugin add telegram-for-codex@telegram-for-codex

Start a new Codex session after installation. Ask “Check my Telegram connection.” Proceed only when the tool reports connected.

Need a different approved endpoint or an existing credential helper? Follow connection setup before using the tools. Do not edit generated plugin caches or paste credentials into a conversation.

This is a GitHub marketplace installation, not a listing in OpenAI's public catalog. See official Codex plugin documentation for supported surfaces and installation behavior.

What ships

.agents/plugins/marketplace.json
plugins/telegram-for-codex/
├── .codex-plugin/plugin.json
├── .mcp.json
├── assets/
├── skills/
│   ├── telegram-conversation/
│   ├── telegram-task-updates/
│   ├── telegram-file-transfer/
│   ├── telegram-bot-ui/
│   └── telegram-bot-testing/
└── scripts/telegram_file_transfer.py

MCP tool	Purpose
telegram_get_connection	Check the authenticated connection.
telegram_send_message	Send a message or short task report.
telegram_request_operator_input	Ask a question with optional choices.
telegram_wait_for_feedback	Resume waiting for the exact request.
telegram_prepare_file_upload	Obtain a limited upload capability.
telegram_send_file	Send a previously uploaded file.
telegram_get_attachment	Obtain a limited download capability.
telegram_test_start	Open an authorized bot test without sending.
telegram_test_send	Send one command or text step through the service bot.
telegram_test_read	Read bounded, subject-owned observations.
telegram_test_finish	Finish/cancel the run without resetting the target.

The remote service owns authentication, recipient binding, durable requests and Telegram delivery. The plugin does not start another bot or polling process. The Python 3 helper runs once per explicitly selected file.

Deliberate limits

• Personal messages/files remain bound to one confirmed private conversation. Separate test tools support explicitly named bots and pre-approved test groups, not arbitrary human recipients or history scraping.
• Live bot testing requires a configured service bot and telegram:bot-testing backend permission. Both bots need Bot-to-Bot Mode for private chats. One shared external identity means test data only, not personal sign-in or isolated target accounts.
• Bot API does not click another bot's inline callbacks. UI clicks, visual rendering and deep-link navigation remain manual; text/metadata observations are not complete human UI-E2E.
• Updates run during an active requested task. No always-on monitoring, hooks, daemon or scheduler.
• A Telegram reply does not approve shell commands or bypass Codex's own permissions.
• File limit: 200,000,000 bytes. A 1 MB round trip was verified; maximum-size transfer has not been tested.
• File capabilities are scoped and short-lived. The helper accepts the canonical Bears origin or its explicit DEV origin, not arbitrary destinations.
• This package includes no backend, credentials, private session data or automatic permission grants.

Development

Plugin assets and instructions live in this repository. The backend is developed and deployed independently. No build step or Node runtime is needed to load the plugin. Artwork includes editable SVG sources alongside PNGs used by the native card.

For changes, keep the seven original MCP names and the four testing names and the file-helper interface compatible with your backend. Use plugin-creator to validate the manifest and skills, then reinstall through Codex's supported plugin update flow. No CI pipeline is required to install this repository.

License and attribution

MIT, copyright © 2026 BearsCLOUD. The plugin was extracted from the Bears Telegram integration and published separately with the owner's approval. The license covers this repository, not the separately deployed backend or third-party services.

Independent community integration by BearsCLOUD. Not an official OpenAI or Telegram product. Codex and Telegram names identify compatible services; the artwork is original to this project.