HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
six-ddc
ccbot
Python2026–2026
six-ddc / ccbot

ccbot

Telegram ↔ tmux bridge for Claude Code: 1 topic = 1 window = 1 session

2Distinct people
2Mentions
0Explicit recommenders
278GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Telegram ↔ tmux bridge for Claude Code: 1 topic = 1 window = 1 session

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2026-02-07 13:30:33 UTC to 2026-02-25 13:25:32 UTC.

012026-02-07 00:00:00 UTC to 2026-02-08 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 72026-02-08 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-09 00:00:00 UTC to 2026-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-10 00:00:00 UTC to 2026-02-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-11 00:00:00 UTC to 2026-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-12 00:00:00 UTC to 2026-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-13 00:00:00 UTC to 2026-02-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-14 00:00:00 UTC to 2026-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-15 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-16 00:00:00 UTC to 2026-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 162026-02-17 00:00:00 UTC to 2026-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-18 00:00:00 UTC to 2026-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-19 00:00:00 UTC to 2026-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 00:00:00 UTC to 2026-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 00:00:00 UTC to 2026-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 00:00:00 UTC to 2026-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-25 00:00:00 UTC to 2026-02-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 25

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 72026-02-07 00:00:00 UTC2026-02-08 00:00:00 UTC110
Feb 82026-02-08 00:00:00 UTC2026-02-09 00:00:00 UTC000
Feb 92026-02-09 00:00:00 UTC2026-02-10 00:00:00 UTC000
Feb 102026-02-10 00:00:00 UTC2026-02-11 00:00:00 UTC000
Feb 112026-02-11 00:00:00 UTC2026-02-12 00:00:00 UTC000
Feb 122026-02-12 00:00:00 UTC2026-02-13 00:00:00 UTC000
Feb 132026-02-13 00:00:00 UTC2026-02-14 00:00:00 UTC000
Feb 142026-02-14 00:00:00 UTC2026-02-15 00:00:00 UTC000
Feb 152026-02-15 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-17 00:00:00 UTC000
Feb 172026-02-17 00:00:00 UTC2026-02-18 00:00:00 UTC000
Feb 182026-02-18 00:00:00 UTC2026-02-19 00:00:00 UTC000
Feb 192026-02-19 00:00:00 UTC2026-02-20 00:00:00 UTC000
Feb 202026-02-20 00:00:00 UTC2026-02-21 00:00:00 UTC000
Feb 212026-02-21 00:00:00 UTC2026-02-22 00:00:00 UTC000
Feb 222026-02-22 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-02-24 00:00:00 UTC000
Feb 242026-02-24 00:00:00 UTC2026-02-25 00:00:00 UTC000
Feb 252026-02-25 00:00:00 UTC2026-02-26 00:00:00 UTC101

What Hacker News says

2 sources
Hi HN, I built CCBot (Command & Control Bot) — a Telegram bot that gives you remote control over AI coding agents (Claude Code, OpenAI Codex CLI, Gemini CLI) running in tmux on your machine. The problem: AI coding agents run in your terminal. When you step away — commuting, on the couch, at dinner — the session keeps working, but you lose visibility and control. Permission prompts pile up. You miss when the agent finishes or gets stuck. =The approach: CCBot doesn't wrap agent SDKs or create isolated API sessions. It sits on top of tmux. Your agent process stays exactly where it is, in a terminal window. CCBot reads its output (from session transcripts, terminal scraping, and hook events) and sends keystrokes to it. You can tmux attach at any time and pick up where you left off — nothing is abstracted away. How it works: Each Telegram Foru
Read the rest
m topic maps to one tmux window running one agent. Messages you type go in as keystrokes; the agent's responses come back as Telegram messages with MarkdownV2 formatting. Interactive prompts (permissions, plan mode, ask-user questions) are rendered as inline keyboard buttons you can tap. Key features: - Multi-provider — Claude Code, Codex, and Gemini in the same session. Each topic can run a different agent. Auto-detects provider from running processes. - Interactive UI from your phone — Permission prompts, AskUserQuestion, ExitPlanMode rendered as tap-to-respond inline keyboards. No more returning to your desk just to hit "y". - Real-time monitoring — Live status line, assistant responses, thinking content, tool use/result pairs streamed to Telegram. - Hook-based event system — 5 Claude Code hook event types (SessionStart, Notification, Stop, SubagentStart, SubagentStop) for instant detection — no polling delay for interactive prompts. - Session lifecycle — Directory browser to create sessions, auto-sync for manually created tmux windows, Fresh/Continue/Resume recovery when sessions die, paginated message history. - Terminal screenshots — Capture the current pane as a PNG image, right from Telegram. - Sessions dashboard — Overview of all running sessions with status and kill buttons. - Agent command passthrough — Send /clear, /compact, /cost, or any slash command directly to the agent. - Multi-instance — Run separate bots per Telegram group on the same machine. Install: `uv tool install ccbot` or `brew install alexei-led/tap/ccbot` Credits: CCBot started as a fork of https://github.com/six-ddc/ccbot, who created the original Telegram-to-Claude-Code bridge — a clever idea that I immediately wanted to build on. The project has since been rewritten with multi-provider support, topic-based architecture, interactive UI, hook event system, and a 1250+ test suite. Thanks to six-ddc for the original idea and implementation that got this started. Tech: Python, python-telegram-bot, tmux, pyte (VT100 emulation), structlog. MIT licensed. Would love feedback — especially from anyone running AI agents on remote machines or headless setups.
In [dead]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.