claude-telegram-supercharged
A drop-in replacement/upgrade for the official Claude Code Telegram plugin that adds richer Telegram behaviors (threading, batching, media handling, reactions/status, history/search/memory, scheduling, daemon management) plus voice input/output (transcription via OpenAI Whisper or local whisper tools; TTS via ElevenLabs). It is integrated as an MCP-style “channel”/plugin for Claude Code and provides tools to the assistant such as reply, react, edit_message, ask_user, get_history, search_messages, clear_history, save_memory, and create_telegraph_page.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses an explicit allowlist/policy concept after pairing. Token is configured into a channel .env file and shell environment takes precedence. Claims about shell injection protection (spawnSync with array args) reduce command-injection risk. However, the provided content does not document transport security details for all outbound connections, secret redaction in logs, or a dependency/Vuln management approach; also subprocess usage for media conversion/transcription implies larger attack surface than plain text bots.
⚡ Reliability
Best When
You want a self-hosted Claude Code Telegram assistant with richer message/thread handling and voice/audio workflows, and you can manage the operational/dependency footprint (Bun, SQLite storage, and optional transcription engines).
Avoid When
You need a standard REST/hosted SaaS API with documented SLAs, or you cannot allow use of third-party providers for transcription/TTS.
Use Cases
- • Running a Claude Code assistant inside Telegram with improved UX (threading, reply context, reactions, inline buttons)
- • Voice-enabled Telegram assistant (STT for inbound voice/audio and optional TTS for replies)
- • Persistent chat context via SQLite history and assistant-accessible tools for retrieval/search and memory summaries
- • Batching and summarizing long message streams from groups
- • Publishing long-form answers to telegra.ph Instant View
- • Scheduling reminders/recurring tasks triggered from Telegram
Not For
- • Production use without reviewing and securing the self-hosted token handling and any subprocess/transcription dependencies
- • Use cases requiring strict data residency/compliance guarantees (not evidenced in provided content)
- • Environments where running external transcription/TTS services (OpenAI/ElevenLabs) is not allowed
Interface
Authentication
Authentication is primarily via Telegram bot token and a pairing/access policy (allowlist described). No OAuth scopes for third-party APIs are described in the provided content; transcription/TTS providers use separate API keys via environment variables (e.g., OPENAI_API_KEY).
Pricing
No pricing tiers for the plugin itself are stated; costs depend on configured external providers.
Agent Metadata
Known Gotchas
- ⚠ MarkdownV2 escaping is handled server-side for assistant output, but parse_mode selection still matters for correct formatting.
- ⚠ Official plugin updates may overwrite the supercharged server.ts; manual re-application steps are required.
- ⚠ Voice transcription can depend on external services or local binaries; failures may result in missing transcription text (audio_path still provided).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for claude-telegram-supercharged.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.