Codex Telegram Bridge — Development skill for Claude Code

codex-telegram-bridge

Part of **[telegram-ai](https://github.com/maleon17/telegram-ai)** — Claude/Codex ↔ Telegram, four ways.

A persistent, multi-account Telegram frontend for [OpenAI Codex](https://developers.openai.com/codex/). It uses your ChatGPT/Codex subscription through the installed Codex CLI—no metered OpenAI API key is required.

Unlike wrappers that launch `codex exec` for every message, this bridge keeps one `codex app-server` alive per Telegram user. Threads survive restarts, and completed turns are delivered as ordinary Telegram messages with an optional collapsible process log.

Features

• Persistent Codex threads: /new, /sessions, /resume.
• Rapid consecutive messages (including forwarded batches) are combined into one prompt.
• Forwarded text and Telegram rich messages keep their source/content context.
• A message sent during an active turn is added to that same turn automatically.
• Clean cancellation through turn/interrupt (/stop).
• Context compaction through thread/compact/start (/compact).
• Detailed /usage: session tokens, context size, subscription limits and reset times.
• Photos and image documents passed to Codex as localImage inputs.
• Agents can return generated files through a tenant-scoped Telegram MCP tool; the bot token remains outside the agent process.
• Model, sandbox and workspace controls per user.
• Deferred restarts that never terminate an active answer.
• Multi-account isolation with a separate CODEX_HOME and App Server process per user.
• No Python packages: the bridge itself uses only the standard library.

Requirements

• Linux with Python 3.10+ and systemd.
• The Codex CLI installed and available as codex.
• The owner's Codex CLI logged in (codex login).
• A Telegram bot token from @BotFather.
• Your numeric Telegram ID (for example from @userinfobot).

Quick install

git cl