No. CodeX Telegram binds to a real Codex thread on your Mac (via Codex App Server), so context stays consistent.
- Codex App (installed + logged in)
- CodeX Telegram (this project)
- Telegram
No Node/Homebrew is required for end users.
CodeX Telegram only receives what you send to the Telegram bot, and forwards it to your local Codex thread.
Please review:
Because your Telegram message can trigger actions that modify files or run commands.
Approvals are a safety boundary: you can confirm or deny from anywhere.
Not reliably today.
CodeX Telegram can only observe tasks that it started itself. Codex currently does not expose a stable “thread is running” signal for arbitrary threads.
Photo input is experimental and depends on your Codex App / App Server version.
If it works on your machine, you'll be able to send a Telegram photo and let Codex see it as an input image.
When thread/list is slow or unavailable, /threads falls back to the local Codex sidebar cache.
That keeps the bot responsive, but some fields (like timestamps) may be missing.