<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telegram on René Zander | AI Automation Consultant</title><link>https://renezander.com/tags/telegram/</link><description>Recent content in Telegram on René Zander | AI Automation Consultant</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://renezander.com/tags/telegram/index.xml" rel="self" type="application/rss+xml"/><item><title>Telegram Bot with Claude API: 30-Line Bash Daemon</title><link>https://renezander.com/blog/telegram-bot-claude-api/</link><pubDate>Tue, 14 Apr 2026 11:00:00 +0200</pubDate><guid>https://renezander.com/blog/telegram-bot-claude-api/</guid><description>&lt;p>I have a Telegram bot wired to Claude Opus 4.7 that I talk to from anywhere. Train, couch, cafe, bed. It reads my TickTick tasks, writes code against my repos, runs shell commands on my VPS, and sends me a morning briefing at 06:30 Madrid time. The whole thing is a bash script and a systemd unit. No frontend. No hosting bill. No auth pages to build.&lt;/p>
&lt;p>This guide walks through exactly how to build one. Two architectures (bash long-polling and a TypeScript webhook server), full runnable code, attachment handling, MCP tool integration, and the security steps most tutorials skip. The primary stack is a Telegram bot Claude API wiring that runs on any Linux box with a few hundred megs of RAM.&lt;/p></description></item></channel></rss>