<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bots on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/bots/</link><description>Recent content in Bots on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 25 Jun 2026 22:13:16 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/bots/index.xml" rel="self" type="application/rss+xml"/><item><title>A Reply Your Bot Loses to a Crash Is One Your User Never Got</title><link>https://startaitools.com/posts/crash-durable-replies-loss-proof/</link><pubDate>Wed, 24 Jun 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/crash-durable-replies-loss-proof/</guid><description>&lt;p&gt;A demo bot answers when nothing goes wrong. A bot people depend on answers when something does.&lt;/p&gt;
&lt;p&gt;The gap between those two is mostly invisible. It lives in the moment your bot has composed a reply, started sending it, and then the process dies — a deploy, an OOM kill, a host reboot. The user is sitting in the channel. The work happened. The answer existed. And it&amp;rsquo;s gone, because it lived only in the memory of a process that no longer exists.&lt;/p&gt;</description></item><item><title>N Bots in One Slack Channel Loop Forever: Three Gates</title><link>https://startaitools.com/posts/bot-loop-circuit-breaker-multi-agent-slack/</link><pubDate>Tue, 23 Jun 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/bot-loop-circuit-breaker-multi-agent-slack/</guid><description>&lt;p&gt;Put two AI agents in the same Slack channel and let each one reply to anything it sees, and you have built a perpetual motion machine. A answers a human. B sees A&amp;rsquo;s message and answers it. A sees B&amp;rsquo;s answer and answers &lt;em&gt;that&lt;/em&gt;. Neither one is wrong. Neither one is broken. They will keep going until you kill a process, because each message is, from Slack&amp;rsquo;s point of view, a legitimately distinct event that deserves a response.&lt;/p&gt;</description></item></channel></rss>