Why AI agents need a durable session layer - and why HTTP isn't enough

What this post added

This post elaborates on the need for a durable session layer for AI agents, highlighting the limitations of HTTP for long-running, complex interactions. It introduces 'durable sessions' as a distinct category of durability that sits between the agent and the user, complementing durable memory and durable execution. The post details the architectural pattern of decoupled pub/sub, explaining how it provides connection reliability, bidirectional communication, and state synchronization by decoupling the agent from the client. It emphasizes that AI Transport is scoped to agent-to-user sessions and not backend agent-to-agent orchestration.