<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Agents on René Zander | AI Automation Consultant</title><link>https://renezander.com/tags/ai-agents/</link><description>Recent content in Ai-Agents 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/ai-agents/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><item><title>n8n AI Agent Workflow Examples: 5 Production Patterns</title><link>https://renezander.com/blog/n8n-ai-agent-workflows/</link><pubDate>Sun, 12 Apr 2026 14:00:00 +0200</pubDate><guid>https://renezander.com/blog/n8n-ai-agent-workflows/</guid><description>&lt;p>I run n8n in production for content ops, email triage, and invoice parsing. The visual canvas is not the point. The point is that triggers, retries, queues, and credentials are free, and I can hand a workflow to a non-engineer to edit prompts without them breaking the integration layer.&lt;/p>
&lt;p>This post is five n8n ai agent workflow examples I actually ship or have shipped for clients. Each one includes the node graph, the Claude prompt, the cost per run, and the production gotchas. No toy demos.&lt;/p></description></item><item><title>AI Agents: Build vs Buy (2026 Decision Framework)</title><link>https://renezander.com/guides/ai-agents-build-vs-buy/</link><pubDate>Sat, 11 Apr 2026 07:00:00 +0000</pubDate><guid>https://renezander.com/guides/ai-agents-build-vs-buy/</guid><description>&lt;p>Every week, a client asks me some version of this question: &amp;ldquo;Should we build our own AI agent or just use [product]?&amp;rdquo;&lt;/p>
&lt;p>The answer is never simple, but after building custom AI agent systems for production use, I have a clear framework for when each path makes sense.&lt;/p>
&lt;h2 id="what-is-an-ai-agent-not-what-you-think">What Is an AI Agent? (Not What You Think)&lt;/h2>
&lt;p>Most businesses asking about AI agents want one of three things:&lt;/p>
&lt;p>&lt;strong>1. An AI chatbot&lt;/strong> that answers questions about their product, knowledge base, or internal docs. This is the most common request. It is also the one most likely to be solved by buying, not building.&lt;/p></description></item><item><title>Production AI Agent Architecture: Patterns That Actually Ship</title><link>https://renezander.com/guides/production-ai-agent-architecture/</link><pubDate>Fri, 10 Apr 2026 08:00:00 +0200</pubDate><guid>https://renezander.com/guides/production-ai-agent-architecture/</guid><description>&lt;p>Most agent tutorials end at &amp;ldquo;the model calls tools in a loop, done.&amp;rdquo; That works for a demo. It falls apart the first time a tool 500s, a user asks something off-script, or the token bill crosses $20 on a single task. Production AI agent architecture is the set of patterns that keep that loop alive when reality hits.&lt;/p>
&lt;p>I run 10 agents in production right now. Bash scripts calling &lt;code>claude -p&lt;/code>, scheduled via systemd timers, reporting outcomes to Telegram. Not fancy. They ship work every day because the architecture around the loop is boring and deliberate. This guide is that playbook: the patterns, the must-haves, the anti-patterns, and the opinionated verdicts on what to use when.&lt;/p></description></item><item><title>GitHub Issue Management AI: Build Claude-Powered Triage That Works</title><link>https://renezander.com/blog/github-issue-management-ai/</link><pubDate>Thu, 09 Apr 2026 14:00:00 +0200</pubDate><guid>https://renezander.com/blog/github-issue-management-ai/</guid><description>&lt;p>Maintainers do not ship software on Tuesday mornings. They triage. They read a new issue, check whether it is a duplicate of something filed three weeks ago, decide whether it is a bug or a question, pick a priority, add two or three labels, and sometimes write a polite comment asking for a repro. Then they do it again for the next issue in the queue. The job is pure admin, and on any active repo it eats real hours every week.&lt;/p></description></item><item><title>AI GitHub Issue Triage with FixClaw: Human in the Loop</title><link>https://renezander.com/guides/fixclaw-ai-github-triage/</link><pubDate>Sat, 28 Mar 2026 14:00:00 +0100</pubDate><guid>https://renezander.com/guides/fixclaw-ai-github-triage/</guid><description>&lt;p>Open source maintainers do not burn out from writing code. They burn out from the inbox. A hundred open issues, half of them duplicates, a third missing a stack trace, and somewhere in there the one real bug that will bite a paying user tomorrow. FixClaw is an &lt;strong>AI GitHub issue triage&lt;/strong> tool built to take that load off without taking the keys away from you.&lt;/p>
&lt;p>This is a product landing page, not a tutorial. If you want to build your own triage system from scratch, skip to the Related Reading at the bottom. If you want &lt;strong>github issue automation&lt;/strong> that reads like a helpful junior maintainer and waits for your approval before posting anything, keep reading.&lt;/p></description></item></channel></rss>