Telegram/Slack bridge for local Codex agents
Running local Codex agents via Telegram is a clever hack for mobile coding sessions.
Lightweight Telegram bridge for Codex on Windows
Windows-only Telegram bridge keeps Codex Desktop threads in sync with mobile chats finally.
Windows developers using Codex Desktop
Slack · Discord · Codex CLI
A. Is a self-contained binary. I know it's not really important, but I like the hygiene.
B. I wanted Codex Desktop on the go, not Codex CLI.
C. I wanted to go back to the work I started on my phone once I return to my desktop. Vice-versa would be nice too, but I don't really need it.
D. I was sick of the usual "agents" that sucked at managing context, poor tool handling, and overall instability. First party harnesses are just better.
E. Native Windows support without a ton of deps. Apparently nobody likes Windows so all the good stuff is made for macOS.
F. Finally, I wanted Codex on the go, not a full-blown agent. I am seriously over agents at this point and I will probably return to them at a later date.
I didn't find anything I liked so I decided to make one.
Features are listed in git. Hopefully someone likes it.
There might/will be bugs. Create issues or submit PRs. Be nice :)
PS: project was entirely done in GPT-5.5-High
Running local Codex agents via Telegram is a clever hack for mobile coding sessions.
Async Telegram workflow for local CLIs when Claude Code Channels hit limits.
Yet another Codex mobile wrapper, but the official app already exists.
Local Codex CLI control via Telegram without opening ports or hosting.
Telegram-to-Claude bridge is nice UX, but continues a local session, not a true multi-device workflow.
Clever use of Claude Channels to push messages—nobody else bridged these two agents yet.