codex-gemini-telegram-bridge

Telegram bridges for running local coding CLIs from a single authorized chat.

I got used to Claude Code Channels and then hit usage limits.

The real problem was not losing a model. It was losing the workflow: sending a coding task from my phone, waiting for the result, and continuing the same thread later without sitting in front of the terminal.

This is not a hosted service and not a generic agent platform. It is a small bridge for people who already work locally and want the async Telegram workflow back.

Each integration runs a local manager process that:

1. polls Telegram Bot API
2. accepts commands from one authorized chat
3. runs the target CLI inside a configured repository
4. sends output back to Telegram

This project is intentionally high-trust by default.

• /run can execute arbitrary commands when allowAnyCommand is enabled
• the sample Codex config uses --dangerously-bypass-approvals-and-sandbox
• the first Telegram chat may auto-register if TELEGRAM_ALLOWED_CHAT_ID is not set

Do not expose this to untrusted chats. Review each integration's config before real use.

This is meant for personal use on a machine you control, not for multi-user or internet-exposed deployment.

• codex-telegram-integration: controls a local Codex CLI session from Telegram
• gemini-telegram-integration_v2: controls a local Gemini CLI session from Telegram

cd codex-telegram-integration
cp local.env.example local.env
# edit local.env and project.json
npm install
npm run start

Or:

cd gemini-telegram-integration_v2
cp local.env.example local.env
# edit local.env and project.json
npm install
npm run start

Telegram:

• fix the failing test in worker/auth.ts
• show git diff
• commit with message: fix auth test

Bridge:

• receives the message
• resumes or starts a local CLI session
• runs inside the co