maleon17

Codex Telegram Bridge — Development skill for Claude Code

Development community

Persistent Codex App Server bridge for Telegram with native drafts and mid-turn steering.

How to install Codex Telegram Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open maleon17/codex-telegram-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Codex Telegram Bridge does

Persistent Codex App Server bridge for Telegram with native drafts and mid-turn steering.

Alternatives in Development

Agentlas One — Turn the persistent Agentlas One personal agent on or off, or rename it 1.1k ★
Premiere Pro MCP — Adobe Premiere Pro MCP — independent, local-first server for supported workflows 292 ★
Quosparr — 🐦 Native menu bar & tray app for macOS, Windows and Linux: track Codex, Claude Code and Grok quotas, resets 288 ★

README

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.