Message in. Work continues.
Telegram triggers the session. Codex keeps running on your machine, inside the workspace you already use.
Telegram bridge for Codex CLI
Run Codex CLI from Telegram.
Text your coding machine. Conexgram keeps Codex running on your own computer while Telegram becomes the fast remote surface for starting, continuing, and checking work.
Runs on your own computer
Persistent Codex sessions
Telegram-controlled workflow
Safe workspace-first defaults
WorkflowTelegram → Conexgram → Codex CLI → local workspace
From your phone
/new ~/projects/app
/status
continue the install patch
On your machine
resume existing Codex thread
inspect workspace and patch files
return progress and final reply
Install
One public install path.
The product page and the installer are the same surface. This command points to the hosted script at `conexgram.com/install.sh`.
curl -fsSL https://conexgram.com/install.sh | bashWhy it works
A small surface over a real local workflow.
No hosted runtime layer.
Your code, credentials, and compute stay local. Telegram is the control surface, not the execution environment.
Built around real sessions.
Resume threads, inspect progress, upload files, and keep context alive between turns.
Operator view
Fast commands. Persistent context.
Start a thread, check status, continue work, or inspect the active workspace. The interaction stays short enough to use from a phone without losing the thread.
/new/status/sessions/workspace/settings/sendfile/stop
Local-first remote control
Your machine stays the machine.
Conexgram is strongest when the value proposition stays obvious: Telegram on top of real Codex CLI sessions running where your code already lives.