Skip to content
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

Workflow SDK now writes over WebSockets on Vercel

The Vercel Workflow SDK has updated to send event writes and stream writes over WebSocket by default starting with version 5.2.0, eliminating the need for one HTTP request per write. This change improves performance, reduces costs, and enables faster AI token streaming—demonstrated by a 4.2× speed improvement in benchmarks. No code changes are required beyond upgrading to workflow@5.2.0 or later. Existing streaming code remains compatible, and in-flight workflows continue on their original deployment. Users should consult the upgrade guide if migrating from version 4.x.

Chat SDK agents can now stream generative UI with json-render

Vercel introduces json-render, enabling Chat SDK agents to generate and stream interactive UI components as JSON specs, which are converted into platform-native cards (e.g., Block Kit on Slack, Adaptive Cards on Teams). The system uses a typed component catalog covering tables, charts, buttons, and more, eliminating the need for separate tools. It supports streaming updates with real-time edits every 500 ms, validates component specs against schemas, and enforces platform-specific message limits to prevent content degradation.

Vercel Schedules is now in public beta

Vercel Schedules is now available in public beta across all plans, enabling users to run tasks on a recurring basis or at a specific time in production, preview, or custom environments. It supports targeting private Vercel Functions, HTTP paths, or Queue topics, with schedules definable in vercel.json or created at runtime. Static schedules use cron expressions and require an experimental trigger to make functions private, while runtime schedules dispatch to Queue topics. Schedules replace Cron Jobs, with billing starting at $5 per 1M runs and $10 per 1M creations on Pro and Enterprise plans, and Hobby plan includes 500 schedule creations and 5,000 runs monthly.

Workflow SDK adds idempotent starts

The Workflow SDK's start() function now allows initiating a workflow run and claiming a hook atomically, eliminating the race condition present in the previous getHookByToken()-then-start() pattern. This change ensures idempotency using a token derived from domain-specific identifiers like order or invoice IDs. Duplicate starts fail safely with a HookConflictError, which includes the conflicting run's ID. The claimed hook is available immediately, enabling early payload buffering and ordered delivery even before execution begins. Inside workflows, createHook with the same token binds to the existing hook without conflict or additional steps. Experimental settings like minRetention prevent late duplicates by keeping tokens reserved after run completion.