update
May 13, 2026
By Teun
Dexgram bridges Telegram topics and Codex Desktop on Windows
Dexgram is a Windows bridge that connects Telegram threaded topics to Codex Desktop threads. It syncs conversations, supports project-bound chats, handles files, and mirrors Codex progress back into Telegram.
Dexgram is a Windows bridge for Codex Desktop that lets users start and continue AI coding conversations from Telegram, then pick them up again in the desktop app. The tool runs as a single Windows binary and maps each Telegram topic to a resumable Codex app-server thread, according to the project page on GitHub.
The main idea is straightforward: a private Telegram bot chat becomes the front end, while Codex Desktop remains the backend. When a user starts a conversation in a Telegram topic, Dexgram creates a Codex thread and stores the mapping so later messages in that topic continue the same thread. Conversations created this way also appear in Codex Desktop’s chat history, which means the thread is visible on both sides.
⚡ New to this?
Dexgram is a bridge between Telegram and Codex Desktop, which is a desktop app for running Codex threads. A thread is just a conversation that can be resumed later, and Telegram “threaded topics” let one bot chat hold multiple separate conversation branches. For non-experts, the news matters because it shows how AI work can be moved between chat apps and desktop tools without losing context.
🦞 OpenClaw angle
If you build self-hosted AI workflows, this is a good pattern to copy: keep a single source of truth for thread state and make the chat app only a control surface. Map each external conversation to one durable backend thread, and persist the mapping by chat ID plus topic or channel ID so users can resume safely.
If your automation handles files, separate attachment staging from prompt submission the way Dexgram does. Also add explicit controls for queueing, steering, and canceling active turns so users can intervene without restarting the whole job. For Windows deployments, prefer per-user startup or scheduled-task installs when the agent needs access to a signed-in desktop session.
Dexgram is designed specifically around Codex Desktop and Codex app-server threads, rather than acting as a generic Telegram bridge. The author says that distinction matters because the bridge is meant to fit Codex Desktop’s own chat history and project flows, including chats that are not tied to a project.
The tool supports both project-bound and projectless chats. For project chats, Dexgram uses fuzzy matching against Codex Desktop project names and shows inline selection buttons if more than one project looks like a match. For chats without a project, it creates a dated workspace under the user’s Documents folder, following Codex Desktop’s “Don’t work in a project” flow.
Dexgram also mirrors Codex activity back into Telegram. According to the project page, users can see an initial reply or plan message, live run-log updates for commands and file edits, and the final answer. Active turns include a Stop button, which interrupts the current Codex turn in the same way as the /stop or /cancel commands.
The bridge handles busy turns by queueing new messages if Codex is already working in that topic. Dexgram still submits the new message to Codex, then gives the Telegram user buttons to steer the queued input into the active turn or delete it before execution. There is also a /steer command for sending follow-up text directly into the active turn.
Dexgram includes file handling for Telegram attachments. It downloads photos and documents to local files before passing them to Codex, stages attachment-only messages for the next prompt, and can upload final-answer file links back to Telegram if the user enables that option. The project page says it does not upload intermediate tool outputs or file edits by default.
The tool also supports Codex goals from Telegram through /goal [objective], provided goals are enabled in the user’s Codex config first. On the Windows side, Dexgram can install itself as a current-user login task through Task Scheduler, with a Startup-folder fallback if Task Scheduler is not available.
Installation is done through a one-line PowerShell command that downloads the latest GitHub release and starts onboarding. The project page says Dexgram puts its binary under the user’s local app data folder, adds it to PATH, creates config and log directories, and can later be updated with dexgram update. The author says the tool is intended for Windows and requires Codex Desktop, a Telegram bot token, and threaded topics enabled for the bot.
