hdcd-telegram: Rust Fix for Claude Telegram Plugin

Claude Code's official Telegram plugin? A 100 MB RAM hog per agent. HyperDev's hdcd-telegram Rust rewrite fixes bugs, slashes overhead, and runs circles around it.

Side-by-side comparison: Bun plugin 100 MB RAM vs hdcd-telegram Rust 5 MB efficiency table

Key Takeaways

  • hdcd-telegram slashes RAM from 100 MB to 5 MB per instance—20x efficiency for multi-agent Claude Code.
  • Full feature parity plus extras like local Whisper transcription and clean shutdown.
  • Drop-in swap preserves settings; signals Rust's rise over JS in AI tooling.

10 Claude Code agents bridging to Telegram. Official plugin: 1 GB RAM burned. hdcd-telegram: 50 MB total. That’s not hype—it’s the table from HyperDev’s GitHub.

Look, if you’re wrangling AI agents, you’ve felt this pain. Claude Code’s Telegram integration—powered by Bun—starts sluggish at 2-3 seconds, leaks zombie processes, and chokes on channels. Issues stack up: #36503 with 24 comments screaming ‘Channels unavailable.’ Bots fake-type forever (#37933). Sessions die after one turn (#36477).

And here’s the killer stat: each instance slurps 100 MB RAM. Scale to a dev fleet or CI pipeline? You’re hemorrhaging gigabytes on JavaScript runtimes.

HyperDev didn’t whine. They rebuilt it in Rust. hdcd-telegram: 3.5 MB binary. 5 MB RAM per instance. Sub-50 ms startup. Clean shutdown—no polling ghosts haunting your stdin.

We built hdcd-telegram – a Rust drop-in replacement with full feature parity.

That’s straight from their announcement. Feature parity? Check: all eight message types (stickers to video notes), reply chunking, threading, attachments, MarkdownV2. Reacts, edits, downloads. Voice-to-text via local Whisper—no cloud leaks. Pairing flows, user allowlists, group @mention gates. Inline keyboards for tool approvals.

Why Does Bun’s Overhead Crush Multi-Agent Claude Setups?

Bun’s fast for JS, sure—but as a runtime embedding? It’s a pig. Rust compiles to metal: no garbage collector drama, no interpreter warmup.

Think 2010s cloud: VMs ate 4 GB per app before Docker’s 10 MB containers flipped the script. Same vibe here. Claude Code agents are the new microservices; bloated bridges kill density. HyperDev runs four in parallel via their SDLC Orchestrator. At scale, Bun’s 1 GB vs. Rust’s 50 MB isn’t optional—it’s survival.

Claude’s JS choice smells like Anthropic’s web-first bias. Fine for browsers. Disaster for servers. This Rust drop-in screams: native binaries win for tools.

Is hdcd-telegram Actually Better Than the Official Plugin?

Benchmarks don’t lie. Official: 100 MB binary + deps. hdcd-telegram: 3.5 MB standalone. Parallel scaling? 20x efficiency. Startup? 40x faster.

Bugs? Official’s channel activation flags flake—workarounds like –dangerously-load-development-channels feel hacky. hdcd-telegram slots right in: same .mcp.json, same .env, same access.json. Swap the command path. Your pairings survive.

Voice transcription stands out—local OpenAI Whisper keeps data private. Official? Silent on that. And no ports, no webhooks: pure outbound HTTPS to Telegram API. Stdio JSON-RPC to Claude. Zombie-free.

But here’s my edge insight, absent from HyperDev’s post: this predicts a Rust renaissance in AI tooling. Remember TensorFlow’s C++ underbelly? Claude Code’s plugin ecosystem will fork to natives—expect npm-like repos of Rust MCP servers by Q2 2025. Anthropic ignores this, their JS stack creaks.

Short setup? Download binary (Linux/macOS/Windows releases ready). mkdir ~/.claude/channels/telegram. Drop your BOT_TOKEN in .env (chmod 600). Patch .mcp.json:

{ “mcpServers”: { “telegram”: { “command”: “/path/to/hdcd-telegram”, “args”: [] } } }

Fire up: claude –dangerously-load-development-channels server:telegram. DM bot, /telegram:access pair . Groups? README covers it.

Existing users: zero migration pain. Reads official files verbatim.

What Happens When Rust Eats JS in Agent Bridges?

Market dynamics shift fast. Claude Code’s multi-agent wave—CI, orchestrators, fleets—demands lightweight plumbing. Bun’s fine for prototypes. Production? Rust’s density rules.

HyperDev open-sourced because “everyone hitting channels bugs deserves a working alternative.” Smart PR, but the real play: position as Claude ecosystem leaders. Their Orchestrator bundles this; watch for paid tiers.

Critique time: Anthropic’s silence on #38259 et al. reeks of neglect. Official plugin’s half-baked—zombies, flags. hdcd-telegram isn’t a patch; it’s superior. If you’re not swapping, you’re subsidizing Bun’s bloat.

Prediction: 50% of heavy Claude users migrate by summer. GitHub stars will explode—it’s already primed.

Scale matters. One agent? Meh. Ten? Game over for JS.


🧬 Related Insights

Frequently Asked Questions

What is hdcd-telegram?

A 3.5 MB Rust binary replacing Claude Code’s 100 MB Telegram plugin—full parity, bug-free, ultra-light.

How do I install hdcd-telegram for Claude Code?

Grab binary from GitHub, set .env token, edit .mcp.json command, launch with dev channels flag. 5 minutes max.

Does hdcd-telegram fix Claude Telegram channel bugs?

Yes—bypasses flags, supports groups/channels fully, no zombies or typing loops.

Marcus Rivera
Written by

Tech journalist covering AI business and enterprise adoption. 10 years in B2B media.

Frequently asked questions

What is hdcd-telegram?
A 3.5 MB Rust binary replacing Claude Code's 100 MB Telegram plugin—full parity, bug-free, ultra-light.
How do I install hdcd-telegram for Claude Code?
Grab binary from GitHub, set .env token, edit .mcp.json command, launch with dev channels flag. 5 minutes max.
Does hdcd-telegram fix Claude Telegram channel bugs?
Yes—bypasses flags, supports groups/channels fully, no zombies or typing loops.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.