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.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
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 unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
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.