TELEGRAM PUB_DATE: 2026.04.20

CONTROL CODEX OR CLAUDE CODE FROM TELEGRAM WITH CLIGATE IN 5 MINUTES

A short guide shows how to trigger Codex or Claude Code on your desktop from Telegram using CliGate, with no server or public IP. This walkthrough wires a Tele...

Control Codex or Claude Code from Telegram with CliGate in 5 minutes

A short guide shows how to trigger Codex or Claude Code on your desktop from Telegram using CliGate, with no server or public IP.

This walkthrough wires a Telegram bot to a local machine via CliGate, so you can kick off headless Codex or Claude Code sessions with slash commands like /cx and /cc. It uses long-polling, which avoids inbound webhooks and ngrok.

The setup is simple: create a BotFather token, enable Telegram in CliGate, pair your phone, then send tasks like “/cx fix tests” to your bot. Events and summaries stream back to chat. Read the steps and commands in the post: How I Control Codex and Claude Code From Telegram — a 5-Minute Setup.

[ WHY_IT_MATTERS ]
01.

Lets on-call engineers trigger quick fixes or diagnostics from a phone without exposing the dev box to the internet.

02.

Adds a low-friction chat interface to coding agents your team already uses.

[ WHAT_TO_TEST ]
  • terminal

    Round-trip latency and reliability of Telegram long-polling across Wi‑Fi, VPN, and cellular networks for multi-step agent runs.

  • terminal

    Security model: run under a restricted OS user, lock working directories, and verify pairing/auth flows and audit logging.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Gate tasks to staging-only directories and read-only prod repos; add chat command allowlists and PagerDuty/SOC sign-off.

  • 02.

    Integrate with existing CI logs or runbooks by posting results to Slack/Jira and persisting transcripts for audits.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Design chat-triggered dev agents early: ephemeral runners behind NAT, no ingress, standardized /cx and /cc task templates.

  • 02.

    Treat Telegram as a thin control plane while keeping all credentials and code execution local to a sandbox VM.

Enjoying_this_story?

Get daily TELEGRAM + SDLC updates.

  • Practical tactics you can ship tomorrow
  • Tooling, workflows, and architecture notes
  • One short email each weekday

FREE_FOREVER. TERMINATE_ANYTIME. View an example issue.

GET_DAILY_EMAIL
AI + SDLC // 5 MIN DAILY