Telegram Codex Bridge v0.3.3

Telegram Codex Bridge v0.3.3

Telegram Codex Bridge lets a private Telegram bot act as a second client for a
Codex Desktop task on Windows.

Highlights

• Route ordinary Telegram text immediately from live turn state, without a
  blocking task-list lookup before every fresh message, steer, or queued turn.
• Recover Desktop-originated final answers from a bounded local rollout tail
  after the shared idle notification. This works even when Codex keeps item and
  completion events private to the Desktop client that started the turn.
• Read at most 16 MB from the end of a task history for completion recovery;
  multi-gigabyte dedicated-task histories are never loaded or sent through the
  shared app-server merely to mirror one reply.
• Accept item completion, turn completion, and agent-message delta event shapes
  for Telegram-originated turns, with per-profile and per-turn deduplication.
• Retry each outbound Telegram reply on transient failures and log exhausted
  delivery attempts without recording message contents or bot credentials.
• Keep state-database-only task inspection for explicit status and recovery
  checks; ordinary inbound routing no longer waits for it.
• Resume indexed-but-cold tasks without returning their turns before starting
  Telegram's fresh turn, with one bounded long timeout for very old histories.
• Deduplicate concurrent task inspections and exponentially back off failed
  Telegram retries instead of piling requests onto a stalled app-server.
• Make the restart shortcut perform a real managed restart even when the TCP
  health endpoint is green, clearing a wedged request queue safely.
• Refuse a full app-server restart while Codex Desktop is still attached, so a
  recovery action cannot strand the open Desktop client or make it hang.
• Recover a listener orphaned by Task Scheduler only after verifying its exact
  bridge runtime path and app-server command line; unknown port owners remain
  untouched.
• Stop only exact installed poller orphans during restart, preventing stale
  service locks from leaving Desktop disconnected after a recovery attempt.
• Make profile status verify the live app-server, Desktop connection, and
  linked task before a skill reports configuration success.
• Keep the safe managed-host restart, poller self-healing, and install-time
  Desktop guard introduced in v0.3.1.
• Keep using the normal Codex Desktop interface while Telegram is connected.
• Plain Telegram messages automatically start a turn when idle or steer the
  active turn while Codex is working.
• Use /fresh, /steer, and /queue when you want explicit delivery behavior.
• Send images and files in either direction.
• Move one shared bot between tasks, or configure separate dedicated bots for
  simultaneous task access.
• Run silently at Windows logon with a bundled Node.js LTS runtime.
• Store Telegram bot tokens in the current Windows user's DPAPI-encrypted local
  data instead of source files, command lines, or Git.

Install

Download TelegramCodexBridgeSetup.exe, verify it against SHA256SUMS.txt,
and run the installer. Setup guides you through entering a freshly generated
BotFather token in a masked local prompt and pairing your Telegram account.
Fully quit and reopen Codex Desktop once after installation.

Important beta notes

• Windows x64 only.
• The installer is not yet code-signed, so Windows may display an Unknown
  Publisher or SmartScreen warning. Verify the SHA-256 before running it.
• Telegram-triggered Codex turns use Full Access with approval policy never.
  Only pair a private bot and Telegram account you control.

See the repository README for configuration, recovery, security boundaries,
uninstall instructions, and example linking prompts.

Telegram Codex Bridge v0.3.1

Telegram Codex Bridge v0.3.1

Telegram Codex Bridge lets a private Telegram bot act as a second client for a
Codex Desktop task on Windows.

Highlights

• Add a safe Restart Telegram Codex Bridge recovery shortcut and make
  npm run service repair the complete managed host instead of launching only
  the Telegram poller.
• Refuse installation while Codex Desktop is still running, before changing
  any bridge or Desktop environment settings.
• Relaunch the managed Telegram poller within seconds if it is killed, with a
  bounded crash-loop fallback to Windows Task Scheduler.
• Report live app-server health and Desktop connectivity in the status tool.
• Keep using the normal Codex Desktop interface while Telegram is connected.
• Plain Telegram messages automatically start a turn when idle or steer the
  active turn while Codex is working.
• Use /fresh, /steer, and /queue when you want explicit delivery behavior.
• Send images and files in either direction.
• Move one shared bot between tasks, or configure separate dedicated bots for
  simultaneous task access.
• Run silently at Windows logon with a bundled Node.js LTS runtime.
• Store Telegram bot tokens in the current Windows user's DPAPI-encrypted local
  data instead of source files, command lines, or Git.

Install

Download TelegramCodexBridgeSetup.exe, verify it against SHA256SUMS.txt,
and run the installer. Setup guides you through entering a freshly generated
BotFather token in a masked local prompt and pairing your Telegram account.
Fully quit and reopen Codex Desktop once after installation.

Important beta notes

• Windows x64 only.
• The installer is not yet code-signed, so Windows may display an Unknown
  Publisher or SmartScreen warning. Verify the SHA-256 before running it.
• Telegram-triggered Codex turns use Full Access with approval policy never.
  Only pair a private bot and Telegram account you control.

See the repository README for configuration, recovery, security boundaries,
uninstall instructions, and example linking prompts.

Telegram Codex Bridge v0.3.0

Telegram Codex Bridge v0.3.0

Telegram Codex Bridge lets a private Telegram bot act as a second client for a
Codex Desktop task on Windows.

Highlights

• Keep using the normal Codex Desktop interface while Telegram is connected.
• Plain Telegram messages automatically start a turn when idle or steer the
  active turn while Codex is working.
• Use /fresh, /steer, and /queue when you want explicit delivery behavior.
• Send images and files in either direction.
• Move one shared bot between tasks, or configure separate dedicated bots for
  simultaneous task access.
• Run silently at Windows logon with a bundled Node.js LTS runtime.
• Store Telegram bot tokens in the current Windows user's DPAPI-encrypted local
  data instead of source files, command lines, or Git.

Install

Download TelegramCodexBridgeSetup.exe, verify it against SHA256SUMS.txt,
and run the installer. Setup guides you through entering a freshly generated
BotFather token in a masked local prompt and pairing your Telegram account.
Fully quit and reopen Codex Desktop once after installation.

Important beta notes

• Windows x64 only.
• The installer is not yet code-signed, so Windows may display an Unknown
  Publisher or SmartScreen warning. Verify the SHA-256 before running it.
• Telegram-triggered Codex turns use Full Access with approval policy never.
  Only pair a private bot and Telegram account you control.

See the repository README for configuration, recovery, security boundaries,
uninstall instructions, and example linking prompts.