Control Codex from Telegram — project-aware sessions, runtime cards, approval flows, and one-line install. Self-hoste...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 71/100. no security policy. 8 open issues make this testable, but not something to trust blind.
AI Agent
Codex
Model
Multiple
Fastest way to find out if telegram-codex-bridge belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/InDreamer/telegram-codex-bridge ~/.claude/agents/telegram-codex-bridgeRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/telegram-codex-bridgeNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ telegram-codex-bridge/ ← installs here └─ settings.json
Control Codex from Telegram — project-aware sessions, runtime cards, approval flows, and one-line install. Self-hosted on your VPS.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: June 1, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.