heyagent and claude-telegram
These are competitors—both bridge Telegram messaging to Claude Code execution, offering similar phone-based codebase control with overlapping functionality, though the latter has achieved significantly higher adoption.
About heyagent
gergomiklos/heyagent
Telegram bridge for Claude Code and Codex CLI
Enables bidirectional messaging between Telegram and Claude Code or Codex CLI, with session persistence and provider switching—users send prompts via Telegram and receive responses locally without server infrastructure. Uses polling-based message fetching with QR-code-assisted bot pairing (via Cloudflare Quick Tunnel) or manual token setup, storing configuration locally while queuing concurrent messages and forwarding attachments to the active provider. Supports dual CLI/Telegram input streams simultaneously, session resumption, and runtime customization of provider permission modes.
About claude-telegram
alexnodeland/claude-telegram
Telegram-to-Claude Code bridge — control your codebase from your phone
Bridges Telegram with Claude Code via a local subprocess orchestrator that streams tool calls and code edits in real time, with granular permission controls (approve once/session/always) and cost tracking per session. Supports job scheduling with cron expressions, multi-project session management, and MCP channel mode for embedding into existing Claude Code instances. Built on Bun runtime with native fetch-only Telegram API integration—no cloud relay, all processing stays on your machine.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work