Telegram Codex Bridge

Codex Console

Control Codex from chat. No terminal. No laptop. Just your phone.

= 24">

---

The Problem

Codex on a VPS is powerful. But reaching it from your phone through a raw SSH session is awful — no project awareness, no structured feedback, no approval flow. Just a wall of text in a tiny terminal.

The Solution

Codex Console turns supported chat platforms into native control surfaces for your existing Codex installation. It's not a second Codex, not a chatbot wrapper — it's a proper remote control.

This repository/package is still named telegram-codex-bridge for compatibility. The product name is Codex Console. The internal shared architecture is Codex Bridge Core. Telegram is the stable first platform pack and default install path; Feishu is a serious current platform pack. That does not mean every surface is fully platform-neutral yet.

flowchart LR
  TG["📱 Telegram"] --> BR["🔗 Codex Console"]
  FS["💬 Feishu"] --> BR
  BR --> CX["⚙️ Codex on your server"]
  CX --> PRJ["📁 Your project files"]

Quick Install

Default: Telegram skill path

curl -fsSL https://raw.githubusercontent.com/InDreamer/telegram-codex-bridge/master/scripts/install-skill-from-github.sh | bash

Then tell Codex:

Use $telegram-codex-linker to set up my Telegram bridge.

The skill handles bridge install, token collection, authorization, and verification. This is the default quick path because Telegram is the stable first pack.

Feishu pack path

curl -fsSL https://raw.githubusercontent.com/InDreamer/telegram-codex-bridge/master/scripts/install-skill-from-github.sh | bash -s -- --pack feishu

Then tell Codex:

Use $feishu-codex-linker to set up my Feishu bridge.

Feishu setup requires a Feishu self-built app, FEISHU_APP_ID / FEISHU_APP_SECRET, long connection, message receive events, and card callbacks. Use the pack-aware admin docs for the exact checklist and verification flow; do not assume every Telegram UX is equally native in Feishu.

Alternative: Direct install

Telegram default:

curl -fsSL https://raw.githubusercontent.com/InDreamer/telegram-codex-bridge/master/scripts/install-from-github.sh | bash -s -- \
  --pack telegram \
  --telegram-token "<YOUR_BOT_TOKEN>" \
  --project-scan-roots "$HOME/projects:$HOME/work"

Feishu:

curl -fsSL https://raw.githubusercontent.com/InDreamer/telegram-codex-bridge/master/scripts/install-from-github.sh | bash -s -- \
  --pack feishu \
  --pack-option app-id="<FEISHU_APP_ID>" \
  --pack-option app-secret="<FEISHU_APP_SECRET>" \
  --project-scan-roots "$HOME/projects:$HOME/work"

Requirements

• An always-on Linux or macOS machine
• An existing Codex installation
• A Telegram bot token for the default pack (from @BotFather), or the matching credentials for another supported pack
• Node >= 24 (if building from source)

Who This Is For

• You already run Codex on a server, desktop, or always-on machine
• You want a cleaner phone workflow than SSH plus tmux
• You prefer self-hosted tools and explicit operator control
• You are okay with a chat control surface being the control plane into a high-trust runtime

What You Get

Project-Aware Sessions

Run /new and choose your project before starting. No blind execution, no guessing which directory you're in.

Runtime Visibility