@ai-sdk/workflow@1.0.0: Vercel's Agent Orchestration Package Hits Stable

Vercel’s @ai-sdk/workflow just shipped its first stable release — 1.0.0. The package gives developers a structured way to orchestrate multi-step AI agent workflows on top of the AI SDK, and this version locks in several breaking changes that were floating in experimental status.

Key changes in 1.0.0:

• Telemetry is now stable. experimental_telemetry drops the prefix. The onChunk telemetry event is removed entirely.
• Node.js 22 minimum. Supported versions: 22, 24, and 26. If you’re on Node 18 or 20, this release won’t run.
• System messages blocked by default. WorkflowAgent now rejects system messages inside prompt or messages, matching generateText / streamText behavior. Set allowSystemInMessages: true to restore the old behavior.
• Renamed APIs. onStepFinish → onStepEnd. context → runtimeContext. Core event types and tool execution events also got new names.
• Agent user-agent tagging. Outgoing requests from agents now include an ai-sdk-agent user-agent segment for usage attribution across tool-loop and workflow modes.
• Flexible tool descriptions. Tool descriptions are no longer rigid — the release notes flag this as a feature, though specifics on the new format aren’t detailed.
• Invalid tool calls preserved. Previously lost invalid tool calls now surface as errors instead of silently disappearing.

The rename wave (onStepFinish, context, event types) is the kind of cleanup you’d expect right before a 1.0 — locking names before semver makes them expensive to change. If you’ve been using the experimental workflow APIs, expect a migration pass through your codebase.

The Node 22 floor is aggressive. Node 20 is still in active LTS until October 2026. Vercel is betting that anyone building agent orchestration is comfortable staying on current runtimes.

1.0.0 is available now on npm. If you’re running workflow agents on the AI SDK, pin your Node version to 22+ and audit your code for the renamed APIs before upgrading.