<?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 Amfelt</title><link>https://amfelt.com/tags/ai-agents/</link><description>Recent content in Ai-Agents on Amfelt</description><generator>Hugo</generator><language>en-us</language><copyright>© 2026 Amfelt Labs B.V.</copyright><lastBuildDate>Sun, 01 Nov 2026 00:11:00 +0000</lastBuildDate><atom:link href="https://amfelt.com/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>The board wants AI. The data is still on the ship.</title><link>https://amfelt.com/blog/why-we-are-building-amfelt/</link><pubDate>Sun, 01 Nov 2026 00:11:00 +0000</pubDate><guid>https://amfelt.com/blog/why-we-are-building-amfelt/</guid><description>A CFO asks the whole company to build with AI, while a modest pilot to collect raw vessel data sits blocked. Why we're building Amfelt for the gap in between.</description></item><item><title>How we keep parallel agents working toward the same plan</title><link>https://amfelt.com/blog/coordinating-parallel-agents/</link><pubDate>Sun, 01 Nov 2026 00:10:00 +0000</pubDate><guid>https://amfelt.com/blog/coordinating-parallel-agents/</guid><description>A commit in August staged one agent session's uncommitted work into another session's change. How we responded with Git worktrees, a guard hook, shared planning documents, a GitHub issue tree, and handovers between sessions.</description></item></channel></rss>