DESKTOP
Codex Desktop
Normal task list + UI
Windows utility · v0.3.1
One Codex task.
In your pocket.
Use a private Telegram bot as a second client for the exact Codex Desktop task you choose. Start, steer, queue, and receive replies while the normal Desktop interface stays yours.
64-bit Windows · Codex Desktop required · No separate Node.js install
LIVE ROUTE / LOCAL LOOPBACK
PRIVATE CHAT
Telegram bot
Fresh · steer · queue
INBOUND OWNER
Only the task you link
Linking another task intentionally moves the shared bot.
The useful bit
Desktop and Telegram are two clients—not two disconnected conversations.
The bridge starts the exact app-server bundled with your installed Codex Desktop package, then connects both surfaces over a loopback-only WebSocket. That keeps the task list visible and the active task steerable from either place.
First run
Four steps, then just talk.
The token never belongs in a Codex prompt. The installer asks for it locally in a masked field.
-
1
Create your bot
Open @BotFather in Telegram, run
/newbot, and keep the token ready. -
2
Install and pair
Fully quit Codex Desktop, run the installer, enter the token in its masked prompt, then send the generated
/paircommand to your bot privately. -
3
Restart Desktop once
Fully quit Codex Desktop—not only its window—then reopen it so Desktop joins the shared app-server.
-
4
Link the task you want
Paste this into that Codex task:
Use $telegram-codex to link this task to my shared Telegram bot.
READY?
TelegramCodexBridgeSetup.exe
Download v0.3.1
Two-way control
Use the message that fits the moment.
Automatic routing
Starts a fresh turn while idle and becomes a native steer while Codex is working.
A new turn
Starts now, or waits behind the active turn if Codex is still working.
Change course now
Adds your message to the active turn using Codex's native steering behavior.
Follow up later
Stores a FIFO fresh turn and sends it only after the current turn fully completes.
Keep the context
Sends photos and files up to 20 MB into the linked task as local attachments.
Outbound alerts
Ask any Codex task to notify you on Telegram without moving the shared inbound link.
Know the boundary
Private by construction, powerful by choice.
The local app-server listens only on 127.0.0.1. Bot tokens are encrypted with
Windows DPAPI for your user account, and messages are accepted only from the private Telegram
user and chat that completed pairing.
Telegram messages still transit Telegram, and Codex work still uses the services configured by Codex Desktop. Treat the bot like remote access to your task.
01No LAN listenerLoopback WebSocket only
02No token in promptsMasked local DPAPI storage
03No CLI replacement
CODEX_CLI_PATH stays empty!Full Access turnsTelegram fresh turns use approval
never and dangerFullAccessMore than one task?
Give the second task its own bot.
The shared bot deliberately follows one inbound task at a time. If two tasks must remain bidirectional simultaneously, create a second BotFather bot and use a dedicated profile.
Use $telegram-codex-dedicated to configure and link a dedicated Telegram bot profile named work to this task.
Recovery
Nothing hidden when something goes wrong.
Will a new link delete or merge my Codex tasks?
No. It only changes which existing task receives future inbound Telegram messages through the shared bot.
Does a console or any foreground window need to stay open?
No. The bridge runs as a hidden per-user Windows logon task. There is no persistent console window.
What if Codex Desktop does not load normally?
Open Restart Telegram Codex Bridge from the Start menu, wait for the green success message, then fully quit and reopen Desktop. If that fails, uninstalling the bridge restores the previous WebSocket environment and never installs a replacement CODEX_CLI_PATH.
How do I inspect it without exposing my token?
Open Telegram Codex Bridge Status from the Start menu. It reports the task, service, and pairing state without printing credentials.
Keep the task. Change the screen.