Durable Sessions vs AI Search Optimization: Which?

What does the Christensen Durable Sessions AI UX Framework do?

The Durable Sessions Framework, introduced by Mike Christensen of Ably at the AI Engineer conference, diagnoses and fixes the core infrastructure problem behind broken AI chat and agent experiences. The framework identifies the Single-Connection Trap — the default pattern where your AI product streams responses over a direct HTTP connection (typically SSE via the Vercel AI SDK or similar), coupling the health of the response stream to the health of one client's connection.

When that connection drops — because a user switches networks on mobile, opens a second tab, or presses a stop button — the stream dies. The framework introduces Durable Sessions: a persistent, shared, stateful layer that sits between your agents and your clients. Agents write events to the session; clients subscribe to the session. Neither holds a direct pipe to the other.

This architectural inversion unlocks three foundational capabilities that separate fragile demos from production-grade AI products: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (clients can steer, interrupt, or cancel an agent mid-generation). The framework also solves the Orchestrator Dual-Purpose Problem in multi-agent architectures by letting every sub-agent write directly to the session, eliminating the orchestrator's relay bottleneck.

What does the AI Search Optimization (AO) Framework do?

The AI Search Optimization framework, from the Marketing Against the Grain podcast (Kipp Bodnar, HubSpot), addresses the seismic shift in how buyers find products and services. Google's AI mode is now the default experience for over 2.5 billion monthly users, and 93% of searches in AI mode end without a single click to any website. Traditional SEO metrics — keyword rankings, referral traffic, page position — are now fundamentally broken as proxies for search performance.

The framework replaces traditional SEO with Answer Engine Optimization (AO): the discipline of becoming the consensus answer that AI synthesizes when a buyer asks a relevant question. The core metric shifts from keyword rankings to AI visibility — whether your brand is mentioned in AI-generated answers and whether it is cited (linked) as a source. Being cited drives 35% more organic clicks and 91% more paid clicks than being uncited.

The framework provides a concrete 90-day playbook: run a Citation Audit across 10–15 buyer prompts in Google AI mode, retire vanity SEO metrics, replace the generic content calendar with a depth-data-specificity content program, expand your distribution footprint across AI-cited platforms (Reddit, LinkedIn, YouTube, press), and assign a Directly Responsible Individual to own the transformation.

How do they compare?

These frameworks operate in entirely separate domains and solve entirely different problems. There is no overlap or conflict between them.

The Durable Sessions Framework is an engineering architecture pattern. It requires you to have an existing AI product with a streaming layer and gives you a redesigned infrastructure. Its audience is engineers, technical product managers, and AI product leaders. The complexity is high — you are changing transport protocols, introducing a pub/sub session layer, and potentially rearchitecting multi-agent communication.

The AO Framework is a marketing and content strategy. It requires you to have a business with a target buyer and gives you a visibility scorecard and content program. Its audience is marketers, founders, and growth practitioners. The complexity is medium — you are changing how you think about search, what content you produce, and where you distribute it.

The Durable Sessions Framework is clearly better for anyone building the product itself. The AO Framework is clearly better for anyone marketing or selling the product. If you are a technical founder doing both, you need both.

Which should you choose?

Choose the Durable Sessions Framework if you are building an AI-powered product and your users experience any of these problems: responses lost on network drops, inability to continue a conversation on a different device, no working stop button, or bottlenecked multi-agent progress updates. Your problem is infrastructure, and this framework gives you the architectural pattern to fix it.

Choose the AI Search Optimization Framework if your organic traffic is declining, your keyword rankings feel disconnected from actual leads, and you suspect your content strategy is built for the old Google. Your problem is visibility in the new AI-driven search landscape, and this framework gives you the 90-day playbook to rebuild.

Choose both if you are a product company that needs its AI experience to work reliably (Durable Sessions) and needs buyers to discover it through AI search (AO). The two frameworks are complementary. One builds a product worth recommending; the other ensures AI recommends it.

Do not confuse these frameworks or treat them as alternatives. Applying the Durable Sessions Framework to a marketing problem or the AO Framework to an infrastructure problem will produce zero results. Match the framework to the problem domain.