Run a Telegram news channel that researches, writes and posts on a schedule

Yonas Mekonnen set Claude Code routines to pick, write and publish AI coding tool news to a Telegram channel three times a day; day one shipped seven posts, none written by hand.

Done withClaude CodeinGitHubTelegram Bot· Nov 21, 2026

What they did

Mekonnen, a backend and AI engineer, wanted a Telegram channel about AI coding tools that ran with no server, no per-token bill and no approval step. He set up Claude Code routines that start a fresh cloud session at 07:00, 12:00 and 16:00 UTC, plus a Sunday roundup with a poll and a monthly pricing cheat sheet. Each run clones a GitHub repo and follows a PROMPT.md file: it scans vendor blogs, changelogs, release trackers, GitHub and web search, scores stories on developer impact, freshness, official sourcing and reach, and writes the best one as a small JSON post. A plain Python script, send.py, then checks the post (length limits, allowed emoji and hashtags, no links, no repeats of an already posted story), finds or draws an image card and sends it through the Telegram Bot API. The repo holds the rules, the list of past posts and a log of every run, and each run commits back to it.

How it went

Day one ended with seven posts: news, tips, an explainer and the pricing sheet, all written by the agent. Three things broke. The first run could not reach github.blog until he widened the cloud environment's network access. One post went out without an image because the image library was broken in the cloud Python and GitHub blocked a page fetch. An explainer packed five numbered tips into one paragraph, which he fixed by hand, the only manual edit so far. Each fix went into send.py as a check with a test rather than into the prompt; the script now has about 90 tests.

Worth knowing

When the model writes a post that breaks a rule, the script refuses it and returns the error, so the run has to fix the post before anything is sent. Routine runs per day are capped by the Claude plan, so he keeps to three posts plus the weekly and monthly jobs and tests locally with a dry-run flag. This is an account of the first day live, not of months of running.

Try it

With Claude Code· 6 parts to fill in

You run my [topic] channel on [Telegram or other platform]. Read the rules and the list of already posted stories in [repo]. Search [list of official sources] for news from the last [hours] hours, score each story on impact, freshness, whether there is an official source and how many people it affects, and pick the best one. Check every fact against the official page. Write it as a JSON post that follows the rules file, then run [send script] to validate and publish it. If the script rejects the post, fix it and try again. If nothing is worth posting, log a skip line with the reason instead. Commit the updated state and log to the repo and stop.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related