claude-tg-bot runs on your own Linux or WSL machine and drives real Claude Code sessions inside tmux. From the phone you see every session, start new ones in any project folder, bring closed ones back — and, above all, answer Claude's interactive questions with buttons.
Claude Code does its best work inside your repository: that project's CLAUDE.md, its skills, its MCP servers, its permission rules. Every session you start here is a session in a real folder on your machine, with all of that already in place — not a detached chat that knows nothing about your setup.
Sessions run in parallel and independently. Starting a task in one project and then opening another does not stop the first — it keeps working, and its answer arrives captioned with its own name. That is the everyday case: a long refactor in one repository while you review a small fix in another.
And it exists because the built-in channels — --remote-control, --channels — are switched off by an organization policy on many corporate accounts. Where they are available they are a perfectly good way to work. Where they are not, this is the way in: it needs nothing enabled on the vendor's side, because it drives from the outside the CLI you already have.
Everything below works from an ordinary Telegram chat — there is no app to install on the phone.
/clear the bot follows the new session id on its own/lang without a restartThree things people reach for instead, and what changes here.
Nothing has to be enabled on the vendor's side. The bot talks to the Claude Code CLI already installed on your machine, so it keeps working when an organization policy switches the built-in channels off — and it keeps working the same way regardless of what the official clients do next.
A terminal app on a phone can reach the session, but answering a highlighted-option dialog with a tiny keyboard is where it falls apart. Here the options become buttons, a wide ASCII diagram is rendered as an image you can zoom, and the answer text comes from the transcript — clean, unwrapped, free of escape codes.
An API wrapper talks to a model; claude-tg-bot drives your Claude Code. The same working directory, the same CLAUDE.md, skills, MCP servers and permission rules, the same subscription quota — and the session you started from the phone is the one you attach to with tmux and carry on at the desk.
One script does the whole install and proves it worked by sending you a message in Telegram. Running it again is also the update path.
git clone https://github.com/vityah1/claude-tg-bot
cd claude-tg-bot
./install.shThe repository, with the full documentation and the install script
Clone the repository, run ./install.sh, answer two questions
Report a bug or propose a feature — contributions are welcome
A new interface language needs no Python at all — only a translation file
Use it, change it, ship it — attribution is all it asks for
The CLI the bot drives — required, and installed separately