Claude Telegram

claude-telegram

A simple and modular Telegram orchestrator on top of Claude Code CLI.

One npm package that connects a Telegram bot to Claude Code via --resume sessions, with whitelist access control and live activity status.

claude-telegram vs OpenClaw

Both are valid choices. claude-telegram is for those who prefer a small, predictable core that they extend themselves.

Installation

1. Get a server — a VPS, a home PC, anything with internet access.

2. Install Claude Code:

3. Install claude-telegram:

Or run without installing via npx claude-telegram.

Alternatively, give Claude the link and let it handle everything:

Quick Start

Don't know your Telegram user ID? Run npx claude-telegram whoami and send a message to the bot.

Config

Create claude-telegram.yaml in your project root:

Environment variables are interpolated with ${VAR_NAME} syntax.

Workspace

The workspace field in config is just the working directory (cwd) for Claude CLI. It can be any directory — claude-telegram doesn't care what's inside. Claude Code will use whatever CLAUDE.md, .claude/agents/, .claude/skills/, and other project files it finds there, exactly as it would in the terminal.

Simple setup

The simplest workspace is a directory with just a CLAUDE.md:

Using an existing project

Any project that works with Claude Code works with claude-telegram — just point workspace at it:

Claude will see the project's CLAUDE.md, agents, skills, commands, MCP servers — everything. You don't need to copy or restructure anything.

Multi-agent setup

Run multiple bots, each pointing to its own project:

Each bot gets its own workspace, sessions, and Telegram token. They share nothing unless you explicitly use add_dirs.

Modules

You can extend the bot without bloating the core by adding optional…