DrSeedon

Kesha Tg Bot — Development skill for Claude Code

Development community

Kesha - Claude Code SDK powered Telegram bot.

How to install Kesha Tg Bot

This entry records only its repository, not the path inside it, so there is no exact command to give. Open DrSeedon/kesha-tg-bot and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Kesha Tg Bot does

Kesha - Claude Code SDK powered Telegram bot.

Alternatives in Development

Telegram — Show Telegram bot status and manage global session 1.3k ★
Claude Prism — An offline-first scientific writing workspace powered by Claude 1.1k ★
Claude Code Bmad Skills — BMAD Method skills for Claude Code - Auto-detection, Memory integration, Slash commands 393 ★

README

Kesha TG Bot

**v2.7.0** | [Changelog](CHANGELOG.md)

Telegram bot powered by **Claude Agent SDK** (official Anthropic SDK), with a second runtime on the **Codex CLI** for emergencies. A full Claude Code CLI experience, but through Telegram.

*[Русский](#русский) ниже.*

What is this

One chat = one agent process with a persistent session. Like chatting in a Claude Code terminal, but via Telegram. All CLAUDE.md, memory files, MCP servers, tools — picked up from the working directory.

Features

Text — regular messages → streaming answer edited live in place
Photos — downloaded, sent to the model for analysis. Albums grouped correctly
Voice — Deepgram STT → text → model
Video notes — ffmpeg extracts audio → Deepgram STT → transcription
Documents — downloads with original filename, the model can read them
Video / Audio — downloads media with original names
Stickers — passes emoji through
Forwards — tagged with [Forwarded from Name]
Replies — quoted text included as [reply: "..."]
Smart tool display — tool calls shown in a separate live bubble with timers, replaced by the next text block
Context tracking — context usage percentage via get_bot_status (Claude; on Codex only after the first turn reports usage)
Two runtimes — Claude (default) and Codex, switched manually with /runtime. Each chat keeps its own session file per runtime, so switching back resumes that runtime's own history
Canonical /limits — forwards Orchestra's exact Claude/Codex/Spark/Grok card, including measured Claude weekly headroom and burn pace
Per-chat edit budget — streaming stays visible under Telegram flood control: when edits are rate-limited it falls back to send+delete instead of freezing
Persistent session — survives bot restarts via storage/sessions/
Debounce — batches rapid messages into one