I started Telegem on December 20, 2025. I didn't plan to build a full Telegram framework. I just wanted something faster than telegram-bot-ruby, something that didn't block, something that felt right in Ruby.
Today, I'm releasing v3.4.0.
What's New
-
Bot API 9.6 full support – managed bots, polls overhaul,
sendMessageDraft, and all the new update types. - Redis session store – for horizontal scaling across multiple webhook instances.
- Translate plugin – built-in translation using the Lingva API.
- Removed concurrent-ruby – lighter footprint, fewer dependencies.
- Better error messages – improved feedback for invalid middleware.
- Ruby 3.1+ support – fully tested and verified.
Why v3.4.0 Matters
The Telegram Bot API changes fast. Most Ruby wrappers lag behind. With v3.4.0, Telegem is fully aligned with Telegram's April 2026 release – managed bots, polls with multiple correct answers, the works.
The Redis store is the other big one. Until now, sessions lived in memory. That's fine for one process. For webhook mode with multiple workers? You needed shared storage. Now you have it.
Looking Back at 4.5 Months
I pushed the first commit on December 20, 2025. Since then, Telegem has grown to:
- 46 versions
- ~71,000 total downloads
- Full async architecture (built on Async, not threads)
- Webhook server with SSL (no Rack required)
- Scenes, sessions, rate limiting, middleware – all the things you expect from a modern framework
Not everyone found it. Not everyone stayed. But thousands of developers tried it, and that's more than I expected when I started.
What's Next
I'm not adding features for the sake of features. Telegem is stable. The next work will be:
- Lowering the Ruby requirement back to 3.1 (v3.4.0 incorrectly bumped it to 3.4 – fixing it in the next patch).
- More docs for advanced patterns.
- Proper plugin system – making it easier for the community to extend the core.
Get It
bash
gem install telegem
Or in your Gemfile:
gem 'telegem', '~> 3.4.0'
Telegem Documentation
Welcome to the comprehensive documentation for Telegem, a modern Ruby framework for building Telegram bots.
Table of Contents
Getting Started
-
README - Main project README
-
Getting Started - Installation and basic setup
-
Core Concepts - Understanding Telegem architecture
Core Components
-
Bot - Main bot class and configuration
-
Context - Update context and response methods
-
Handlers - Command, hears, and event handlers
-
Middleware - Request processing pipeline
-
Scenes - Multi-step conversation flows
-
Sessions - Data persistence between updates
API & Types
-
API - Telegram API client usage
-
Types - Type-safe API response handling
-
Keyboards - Inline and reply keyboard DSL
Advanced Features
-
Plugins - Built-in and custom plugins
-
Webhooks - Production webhook deployment
-
Error Handling - Comprehensive error management
-
Testing - Unit and integration testing
-
Deployment - Production deployment guides
Examples & Guides
-
Examples - Complete bot examples
-
Troubleshooting - Common issues and solutions
-
Contributing - Development guidelines
-
Changelog…
Community
Join the conversation and get help in the official group:
Join the Telegram Group
I don't know where Telegem will be a year from now. But I know it's already a better foundation than anything else in Ruby for building Telegram bots.
I'm curious—for those building bots in Ruby, what's your biggest pain point with current libraries? I'd love to see if Telegem can solve it for you.
– ZenDrx
Top comments (0)