ClaudeBot CLI
A Telegram bot drives Claude Code on your computer: you message the chat and the agent edits the project and streams the reply.
- 65 ★ on the repository
- Last commit
Broad access
Why this level
- A Telegram message triggers an agent that edits files and runs commands on your computer.
- With `/pair` the agent gets file access on a remote machine over WebSocket.
Install
- Works in
Manual install
npx claudebot-appDownloads the project, runs the setup wizard and starts the bot.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A Telegram message triggers an agent that edits files and runs commands on your computer.
- With `/pair` the agent gets file access on a remote machine over WebSocket.
This is third-party code. Review the repository files before installing.
What it does
ClaudeBot runs the Claude Code, Gemini and Codex CLIs already installed on your machine and connects them to a Telegram chat. Replies stream into the chat, edits land in real files and repositories, and sessions are kept per project and continued with `--resume`. The kit adds a task queue with locks between bots, a `/deep` mode with Opus and subagents, parallel runs in separate git worktrees, plugins that cost no tokens, voice input through local Sherpa-ONNX and a remote machine connected with `/pair`. No API keys or cloud relay are needed.
Who it is for. Developers who want to assign Claude Code tasks from a phone while keeping the whole pipeline on their own machine.
Good fit when
- Ten tasks are queued and you walk away, receiving reports in Telegram.
- Several bots work on one project in separate git worktrees.
- A voice message becomes a task for the agent.
- A remote machine is attached with `/pair` and the agent reads and writes files there.
Not a fit when
- You need a one-off chat with no access to code and files.
- The computer with the Claude CLI cannot stay on.
- File access triggered by a messenger message is unacceptable to you.
Example request
Queue a task: update the project dependencies and send the result to Telegram.Limitations
Node.js version 20 or newer and a logged-in Claude CLI are required. Gemini CLI, Python 3.11 or newer and sherpa-onnx are optional. Voice input works once sherpa-onnx is installed. Bot access is guarded by chat ID, bcrypt and rate limits, and the agent cannot delete `.env`, `.sessions.json` or `.pairings.json`. The bot drives real files and commands, so keep the Telegram token and the allowed chat list secret.
How to disable. Stop the bot process and delete the project directory together with `.env`. Revoke the bot token in Telegram through BotFather.
FAQ
How do I start ClaudeBot?
Run `npx claudebot-app`. It downloads the project, runs the setup wizard and starts the bot; ffmpeg is bundled.
Are API keys required?
No. The bot calls installed CLIs, so it works through your Claude CLI login.
How do I run several bots on one project?
Set `WORKTREE_BRANCH=bot1` in `.env`: the bot creates an isolated git worktree and does not interfere with others.
What does the /deep command do?
It switches the bot to Opus with subagents to investigate a task from several angles.
How does the bot protect access?
It checks the chat ID, stores the password with bcrypt and rate-limits requests. The agent cannot delete `.env`, `.sessions.json` or `.pairings.json`.
Discussion
No questions or reviews yet.
Related
CLI toolsUntether bridges Claude Code, Codex and OpenCode with Telegram: voice or text tasks, live progress, approvals with buttons.
Connects Claude Code, Cursor, Codex or OpenCode to Telegram, Slack and Discord: teammates message a bot, an agent replies
Upgrade for the official Claude Code Telegram plugin: voice messages, live progress, buttons, memory and an agents board
A plugin that makes Claude Code a background assistant: scheduled tasks, Telegram, Discord and Slack replies, a web dashboard.
A CLI for driving a Telegram account from the terminal: a daemon, JSON output for agents, webhook events and a Claude Code skill.
A CLI that keeps Claude Code agents running around the clock in PTY sessions, steered from Telegram, a dashboard and cron.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| ClaudeBot (this card) | no | 65 | |
| Claude Code Telegram Bot | no | 2,823 | a minimal bridge between a chat and Claude Code; ClaudeBot adds a queue, git worktrees, voice and plugins |
| OpenCode Telegram Bot | no | 1,352 | a bot for OpenCode; ClaudeBot works with Claude Code, Gemini and Codex |
README in short
The project presents itself as a command center on a phone rather than an API wrapper. The base is described in sections on architecture, AI directives and a four-layer memory.