maleon17

Claude Telegram Bridge — Communication skill for Claude Code

Communication community

Telegram bridge for Claude Code — chat with Claude via your own subscription (Pro/Max/Team), with live streaming, multi-tenant accounts, and session management.

How to install Claude Telegram Bridge

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

What Claude Telegram Bridge does

Telegram bridge for Claude Code — chat with Claude via your own subscription (Pro/Max/Team), with live streaming, multi-tenant accounts, and session management.

Alternatives in Communication

Lark Coding Agent Bridge — Bot that bridges Feishu/Lark messenger with a local Claude Code or Codex CLI 2.4k ★
Claudix - Claude Code For VSCode — by Haleclipse - A VSCode extension that brings Claude Code directly into your editor with interactive chat int 1k ★
Claude Code Webui — Web-based interface for Claude CLI with streaming chat responses 969 ★

README

claude-telegram-bridge

Part of **[telegram-ai](https://github.com/maleon17/telegram-ai)** — Claude/Codex ↔ Telegram, four ways.

A Telegram bridge for [Claude Code](https://claude.com/claude-code) — message Claude from Telegram using your own Claude subscription (Pro/Max/Team), not a metered API key.

Drives `claude -p --output-format=stream-json` per message and streams progress back live, with real session management, multi-tenancy (each whitelisted person gets their own isolated Claude account), and support for photos/files in both directions.

Features

Live progress streaming — a "thinking" preview animates in Telegram while Claude works (via Bot API's sendMessageDraft), showing the current tool call and its result as separate code blocks, before the final answer and full process log land as normal messages.
Sessions — /new, /sessions, /resume map onto Claude Code's own --resume/session mechanism, so conversations persist across bot restarts.
Multi-tenant — a simple whitelist.txt gates access. Anyone besides the owner who's whitelisted goes through their own claude auth login (a button + pasted code, right in the chat) and gets a fully isolated Claude account (own subscription, own sessions, own usage) — no shared billing.
Model / permission control — /model to switch between Opus/Sonnet/Haiku/Fable and specific versions, /mode to switch between auto-approve and a real approve/deny gate for tool calls.
Files & photos — incoming photos/documents are downloaded and handed to Claude to read natively; outgoing files Claude creates (or mentions by path) get sent back as Telegram attachments automatically.
Explicit file delivery — send_telegram_file lets an agent return a file deliberately from CLAUDE_TELEGRAM_OUTBOX, bound to its current chat without exposing the bot token.
Rich messages — incoming Telegram "rich messages" (tables, collapsible sections, etc.) are converted to Markdown so th