<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sessions on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/sessions/</link><description>Recent content in Sessions on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Thu, 07 May 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/sessions/index.xml" rel="self" type="application/rss+xml"/><item><title>Sessions Are Not Missions</title><link>https://notes.karlmcguinness.com/notes/sessions-are-not-missions/</link><pubDate>Thu, 07 May 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/sessions-are-not-missions/</guid><description>Modern agent harnesses make work durable across restarts, devices, background jobs, and sub-agents. That durability is a runtime property, not a governance property. A session answers where the agent can continue working. A mission answers why the agent is allowed to keep working. Conflating them is a central failure mode of long-running autonomous agent systems.</description></item></channel></rss>