codex - 💡(How to fix) Fix Feature request: official Telegram integration/plugin for Codex CLI [1 comments, 2 participants]

Feature request

Please consider providing an official Telegram integration/plugin for Codex CLI.

Motivation

Codex CLI is already very useful in a terminal-first workflow, but there is currently no official way to connect it to Telegram as a chat interface. Many users run agents on a Mac/Linux machine or a server and want to interact with Codex remotely from their phone without keeping a terminal open.

A Telegram integration would make Codex CLI much more practical for:

• remote coding assistance while away from the computer;
• receiving long-running task notifications and summaries;
• sending follow-up instructions from mobile;
• sharing files, screenshots, voice notes, or quick text prompts into a running coding workflow;
• self-hosted personal assistant setups where Telegram is the main control surface.

Proposed solution

An official plugin could provide a supported bridge between Codex CLI and Telegram Bot API, for example:

• configure with a Telegram bot token and allowed user/chat IDs;
• map Telegram messages to Codex CLI sessions;
• stream or send final responses back to Telegram;
• support file/image attachments when possible;
• expose safe controls for approvals, cancellation, and session reset;
• avoid duplicate polling/webhook instances and document deployment patterns.

Why official support matters

Community wrappers can work, but messaging integrations touch authentication, command execution, file access, and approval flows. An official plugin or documented reference implementation would give users a safer and more reliable path than ad-hoc scripts.

Thanks for considering it.