Topics
/
AI Stack

AI Stack

AI Stack

Filter by

8 items

AI Stack

AI Stack

Why Vercel AI SDK can't stream to multiple devices

SSE is a one-to-one connection. Delivering the same AI generation to multiple clients or devices requires a broadcast layer that SSE cannot provide.

WebSockets on Vercel: why serverless functions can't host them

Vercel serverless functions can't host WebSocket connections, even with Fluid Compute. Options and how to connect a WebSocket provider to Vercel AI SDK.

Durable sessions for Vercel AI SDK applications

Vercel AI SDK handles orchestration and UI well. SSE breaks behind enterprise proxies and for long-running agents. ChatTransport lets you swap it out.

Why Temporal workflows need a frontend delivery layer

Temporal crash-proofs backend workflows. A durable sessions layer handles browser delivery, reconnect replay, multi-device fan-out, and offline notifications.

Why Vercel AI SDK stop() doesn't cancel the stream

Calling stop() closes the client-side connection but doesn't cancel server-side generation. Here's why it fails and how to fix it.

Vercel AI SDK ChatTransport: implementing a custom WebSocket transport

The ChatTransport interface is the plug-in point Vercel built into AI SDK 5 to separate transport from application logic.

Vercel AI SDK resumable-stream: what it covers and what it doesn't

Vercel's resumable-stream covers page reloads only. Tab switches, mobile backgrounding, and device switches lose the stream. Also incompatible with stop().

Why AI chat history disappears between sessions

Vercel AI SDK stores messages in component state. When the page reloads or user returns, the history is gone. How to add durable persistence to AI applications