<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>daemons on SnoWake.dev - Cloud, AI, GridTech, Security, Drones, 3D Printing & More</title><link>https://snowake.dev/tags/daemons/index.xml</link><description>Recent content in daemons on SnoWake.dev - Cloud, AI, GridTech, Security, Drones, 3D Printing & More</description><generator>Hugo -- 0.151.0</generator><language>en-us</language><lastBuildDate>Sat, 28 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://snowake.dev/tags/daemons/index.xml" rel="self" type="application/rss+xml"/><item><title>The Daemon Moves Out: Why MCP Was the Wrong Home for the Pipeline</title><link>https://snowake.dev/posts/daemon-moves-out-mcp-extraction/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><guid>https://snowake.dev/posts/daemon-moves-out-mcp-extraction/</guid><description>Five months after building the Research Curation Daemon as an MCP server, I extracted the agent into a standalone process with its own HTTP API. The protocol wasn't the problem. The hosting was.</description></item></channel></rss>