workflow 4.2.0-beta.72 → 4.2.0-beta.74

package/README.md

@@ -2,7 +2,7 @@
   <a href="https://useworkflow.dev">
     <picture>
       <source media="(prefers-color-scheme: dark)" srcset="https://useworkflow.dev/workflow-circle-symbol-dark.svg">
-      <img alt="Workflow DevKit logo" src="https://useworkflow.dev/workflow-circle-symbol-light.svg" height="128">
+      <img alt="Workflow SDK logo" src="https://useworkflow.dev/workflow-circle-symbol-light.svg" height="128">
     </picture>
   </a>
   <h1>Workflow Development Kit</h1>
@@ -22,15 +22,15 @@ Visit [https://useworkflow.dev](https://useworkflow.dev) to view the full docume
 
 ## Community
 
-The Workflow DevKit community can be found on [GitHub Discussions](https://github.com/vercel/workflow/discussions), where you can ask questions, voice ideas, and share your projects with other people.
+The Workflow SDK community can be found on [GitHub Discussions](https://github.com/vercel/workflow/discussions), where you can ask questions, voice ideas, and share your projects with other people.
 
 ## Contributing
 
-Contributions to Workflow DevKit are welcome and highly appreciated. Please use GitHub [issues](https://github.com/vercel/workflow/issues) and [discussions](https://github.com/vercel/workflow/discussions) to collaborate with the team and wider community.
+Contributions to Workflow SDK are welcome and highly appreciated. Please use GitHub [issues](https://github.com/vercel/workflow/issues) and [discussions](https://github.com/vercel/workflow/discussions) to collaborate with the team and wider community.
 
 ## Author list
 
-Workflow DevKit was built by engineers at [Vercel](https://vercel.com) and the [Open Source Community](https://github.com/vercel/workflow/graphs/contributors).
+Workflow SDK was built by engineers at [Vercel](https://vercel.com) and the [Open Source Community](https://github.com/vercel/workflow/graphs/contributors).
 
 The initial core contributing engineers are:
 
@@ -42,12 +42,12 @@ The initial core contributing engineers are:
 - Peter Wielander ([@VaguelySerious](https://github.com/VaguelySerious))
 - Pranay Prakash ([@pranaygp](https://github.com/pranaygp))
 
-The Workflow DevKit logo was designed by Cecilio Ruiz [@ceciliorz](https://x.com/ceciliorz)
+The Workflow SDK logo was designed by Cecilio Ruiz [@ceciliorz](https://x.com/ceciliorz)
 
 ---
 
 ## Security
 
-If you believe you have found a security vulnerability in Workflow DevKit, we encourage you to **_responsibly disclose this and not open a public issue_**.
+If you believe you have found a security vulnerability in Workflow SDK, we encourage you to **_responsibly disclose this and not open a public issue_**.
 
 To participate in our Open Source Software Bug Bounty program, please email [responsible.disclosure@vercel.com](mailto:responsible.disclosure@vercel.com). We will add you to the program and provide further instructions for submitting your report.

package/docs/ai/defining-tools.mdx

@@ -1,6 +1,6 @@
 ---
 title: Patterns for Defining Tools
-description: Common patterns for defining tools in durable AI agents using Workflow DevKit.
+description: Common patterns for defining tools in durable AI agents using Workflow SDK.
 type: guide
 summary: Define step-level and workflow-level tools for durable AI agents with stream writing and context access.
 prerequisites:
@@ -12,7 +12,7 @@ related:
   - /docs/api-reference/workflow/get-writable
 ---
 
-This page covers the details for some common patterns when defining tools for AI agents using Workflow DevKit.
+This page covers the details for some common patterns when defining tools for AI agents using Workflow SDK.
 
 Using DurableAgent, we model most tools as steps. These can be anything from a simple function call to a entire multi-day long workflow.
 

package/docs/ai/human-in-the-loop.mdx

@@ -15,7 +15,7 @@ related:
 
 A common pre-requisite for running AI agents in production is the ability to wait for human input or external events before proceeding.
 
-Workflow DevKit's [webhook](/docs/api-reference/workflow/create-webhook) and [hook](/docs/api-reference/workflow/define-hook) primitives enable "human-in-the-loop" patterns where workflows pause until a human takes action, allowing smooth resumption of workflows even after days of inactivity, and provides stability across code deployments.
+Workflow SDK's [webhook](/docs/api-reference/workflow/create-webhook) and [hook](/docs/api-reference/workflow/define-hook) primitives enable "human-in-the-loop" patterns where workflows pause until a human takes action, allowing smooth resumption of workflows even after days of inactivity, and provides stability across code deployments.
 
 If you need to react to external events programmatically, see the [hooks](/docs/foundations/hooks) documentation for more information. This part of the guide will focus on the human-in-the-loop pattern, which is a subset of the more general hook pattern.
 

package/docs/ai/index.mdx

@@ -2,7 +2,7 @@
 title: Building Durable AI Agents
 description: Build AI agents that survive crashes, scale across requests, and maintain state with durable LLM tool-call loops.
 type: overview
-summary: Convert a basic AI chat app into a durable, resumable agent using Workflow DevKit.
+summary: Convert a basic AI chat app into a durable, resumable agent using Workflow SDK.
 related:
   - /docs/foundations/workflows-and-steps
   - /docs/foundations/streaming
@@ -15,11 +15,11 @@ related:
 
 AI agents are built on the primitive of LLM and tool-call loops, often with additional processes for data fetching, resource provisioning, or reacting to external events.
 
-Workflow DevKit makes your agents production-ready, by turning them into durable, resumable workflows. It transforms your LLM calls, tool executions, and other async operations into retryable, scalable, and observable steps.
+Workflow SDK makes your agents production-ready, by turning them into durable, resumable workflows. It transforms your LLM calls, tool executions, and other async operations into retryable, scalable, and observable steps.
 
 <AgentTraces />
 
-This guide walks you through converting a basic AI chat app into a durable AI agent using Workflow DevKit.
+This guide walks you through converting a basic AI chat app into a durable AI agent using Workflow SDK.
 
 ## Why Durable Agents?
 
@@ -30,20 +30,20 @@ Aside from the usual challenges of getting your long-running tasks to be product
 - **Resumability**: Resuming streams requires not just storing your messages, but also storing streams, and piping them across services.
 - **Human-in-the-loop**: Your client, API, and async job orchestration need to work together to create, track, route to, and display human approval requests, or similar webhook operations.
 
-Workflow DevKit provides all of these capabilities out of the box. Your agent becomes a workflow, your tools become steps, and the framework handles interplay with your existing infrastructure.
+Workflow SDK provides all of these capabilities out of the box. Your agent becomes a workflow, your tools become steps, and the framework handles interplay with your existing infrastructure.
 
 ## Getting Started
 
 To make an Agent durable, we first need an Agent, which we'll be setting up here. If you already have an app you'd like to follow along with, you can skip this section.
 
-For our example, we'll need an app with a simple chat interface and an API route calling an LLM, so that we can add Workflow DevKit to it. We'll use the [Flight Booking Agent](https://github.com/vercel/workflow-examples/tree/main/flight-booking-app) example as a starting point, which comes with a chat interface built using Next.js, AI SDK, and Shadcn UI.
+For our example, we'll need an app with a simple chat interface and an API route calling an LLM, so that we can add Workflow SDK to it. We'll use the [Flight Booking Agent](https://github.com/vercel/workflow-examples/tree/main/flight-booking-app) example as a starting point, which comes with a chat interface built using Next.js, AI SDK, and Shadcn UI.
 
 <Steps>
 
 <Step>
 ### Clone example app
 
-We'll need an app with a simple chat interface and an API route calling an LLM, so that we can add Workflow DevKit to it. For the follow-along steps, we'll use the [Flight Booking Agent](https://github.com/vercel/workflow-examples/tree/main/flight-booking-app) example as a starting point, which comes with a chat interface built using Next.js, AI SDK, and Shadcn UI.
+We'll need an app with a simple chat interface and an API route calling an LLM, so that we can add Workflow SDK to it. For the follow-along steps, we'll use the [Flight Booking Agent](https://github.com/vercel/workflow-examples/tree/main/flight-booking-app) example as a starting point, which comes with a chat interface built using Next.js, AI SDK, and Shadcn UI.
 
 If you have your own project, you can skip this step, and simply apply the changes of the following steps to your own project.
 
@@ -219,7 +219,7 @@ export default function ChatPage() {
 
 </Steps>
 
-## Integrating Workflow DevKit
+## Integrating Workflow SDK
 
 Now that we have a basic agent using AI SDK, we can modify it to make it durable.
 
@@ -228,7 +228,7 @@ Now that we have a basic agent using AI SDK, we can modify it to make it durable
 
 ### Install Dependencies
 
-Add the Workflow DevKit packages to your project:
+Add the Workflow SDK packages to your project:
 
 ```package-install
 npm i workflow @workflow/ai

package/docs/ai/resumable-streams.mdx

@@ -16,7 +16,7 @@ When building chat interfaces, it's common to run into network interruptions, pa
 
 Where a standard chat implementation would require the user to resend their message and wait for the entire response again, workflow runs are durable, and so are the streams attached to them. This means a stream can be resumed at any point, optionally only syncing the data that was missed since the last connection.
 
-Resumable streams come out of the box with Workflow DevKit, however, the client needs to recognize that a stream exists, and needs to know which stream to reconnect to, and needs to know where to start from. For this, Workflow DevKit provides the [`WorkflowChatTransport`](/docs/api-reference/workflow-ai/workflow-chat-transport) helper, a drop-in transport for the AI SDK that handles client-side resumption logic for you.
+Resumable streams come out of the box with Workflow SDK, however, the client needs to recognize that a stream exists, and needs to know which stream to reconnect to, and needs to know where to start from. For this, Workflow SDK provides the [`WorkflowChatTransport`](/docs/api-reference/workflow-ai/workflow-chat-transport) helper, a drop-in transport for the AI SDK that handles client-side resumption logic for you.
 
 ## Implementing stream resumption
 

package/docs/ai/sleep-and-delays.mdx

@@ -14,7 +14,7 @@ related:
 
 AI agents sometimes need to pause execution in order to schedule recurring or future actions, wait before retrying an operation (e.g. for rate limiting), or wait for external state to be available.
 
-Workflow DevKit's `sleep` function enables Agents to pause execution without consuming resources, and resume at a specified time, after a specified duration, or in response to an external event. Workflow operation that suspend will survive restarts, new deploys, and infrastructure changes, independent of whether the suspense takes seconds or months.
+Workflow SDK's `sleep` function enables Agents to pause execution without consuming resources, and resume at a specified time, after a specified duration, or in response to an external event. Workflow operation that suspend will survive restarts, new deploys, and infrastructure changes, independent of whether the suspense takes seconds or months.
 
 <Callout type="info">
 See the [`sleep()` API Reference](/docs/api-reference/workflow/sleep) for the full list of supported duration formats and detailed API documentation, and see the [hooks](/docs/foundations/hooks) documentation for more information on how to resume in response to external events.
@@ -22,7 +22,7 @@ See the [`sleep()` API Reference](/docs/api-reference/workflow/sleep) for the fu
 
 ## Adding a Sleep Tool
 
-Sleep is a built-in function in Workflow DevKit, so exposing it as a tool is as simple as wrapping it in a tool definition. Learn more about how to define tools in [Patterns for Defining Tools](/docs/ai/defining-tools).
+Sleep is a built-in function in Workflow SDK, so exposing it as a tool is as simple as wrapping it in a tool definition. Learn more about how to define tools in [Patterns for Defining Tools](/docs/ai/defining-tools).
 
 <Steps>
 

package/docs/ai/streaming-updates-from-tools.mdx

@@ -14,7 +14,7 @@ related:
 
 After [building a durable AI agent](/docs/ai), we already get UI message chunks for displaying tool invocations and return values. However, for long-running steps, we may want to show progress updates, or stream step output to the user while it's being generated.
 
-Workflow DevKit enables this by letting step functions write custom chunks to the same stream the agent uses. These chunks appear as data parts in your messages, which you can render however you like.
+Workflow SDK enables this by letting step functions write custom chunks to the same stream the agent uses. These chunks appear as data parts in your messages, which you can render however you like.
 
 As an example, we'll extend out Flight Booking Agent to use emit more granular progress updates while searching for flights.
 

package/docs/api-reference/index.mdx

@@ -1,13 +1,16 @@
 ---
 title: API Reference
-description: Complete reference for all Workflow DevKit functions and primitives by package.
+description: Complete reference for all Workflow SDK functions and primitives by package.
 type: overview
 summary: Browse all available functions and primitives organized by package.
 ---
 
-All the functions and primitives that come with Workflow DevKit by package.
+All the functions and primitives that come with Workflow SDK by package.
 
 <Cards>
+    <Card title="Workflow Globals" href="/docs/api-reference/workflow-globals">
+        Global APIs available inside workflow functions, including deterministic APIs, Web Platform APIs, and environment variables.
+    </Card>
     <Card title="workflow" href="/docs/api-reference/workflow">
         Core workflow primitives including steps, context management, streaming, webhooks, and error handling.
     </Card>
@@ -15,7 +18,10 @@ All the functions and primitives that come with Workflow DevKit by package.
         API reference for runtime functions from the `workflow/api` package.
     </Card>
     <Card title="workflow/next" href="/docs/api-reference/workflow-next">
-        Next.js integration for Workflow DevKit that automatically configures bundling and runtime support.
+        Next.js integration for Workflow SDK that automatically configures bundling and runtime support.
+    </Card>
+    <Card title="workflow/errors" href="/docs/api-reference/workflow-errors">
+        Semantic error types for handling workflow storage backend failures.
     </Card>
     <Card title="@workflow/serde" href="/docs/api-reference/workflow-serde">
         Serialization symbols for custom class serialization in workflows.

package/docs/api-reference/meta.json

@@ -1,4 +1,13 @@
 {
   "title": "API Reference",
-  "pages": ["...", "workflow-errors", "workflow-serde", "workflow-ai", "vitest"]
+  "pages": [
+    "workflow-globals",
+    "workflow",
+    "workflow-api",
+    "workflow-next",
+    "workflow-errors",
+    "workflow-serde",
+    "workflow-ai",
+    "vitest"
+  ]
 }

package/docs/api-reference/workflow/index.mdx

@@ -20,7 +20,7 @@ npm i workflow
 
 ## Functions
 
-Workflow DevKit contains the following functions you can use inside your workflow functions:
+Workflow SDK contains the following functions you can use inside your workflow functions:
 
 <Cards>
     <Card href="/docs/api-reference/workflow/get-workflow-metadata" title="getWorkflowMetadata()">
@@ -51,7 +51,7 @@ Workflow DevKit contains the following functions you can use inside your workflo
 
 ## Error Classes
 
-Workflow DevKit includes error classes that can be thrown in a workflow or step to change the error exit strategy of a workflow.
+Workflow SDK includes error classes that can be thrown in a workflow or step to change the error exit strategy of a workflow.
 
 <Cards>
     <Card href="/docs/api-reference/workflow/fatal-error" title="FatalError()">

package/docs/api-reference/workflow-ai/durable-agent.mdx

@@ -204,7 +204,7 @@ export default OutputSpecification;`}
 - **Durable Execution**: Agents can be interrupted and resumed without losing state
 - **Flexible Tool Implementation**: Tools can be implemented as workflow steps for automatic retries, or as regular workflow-level logic
 - **Stream Processing**: Handles streaming responses and tool calls in a structured way
-- **Workflow Native**: Fully integrated with Workflow DevKit for production-grade reliability
+- **Workflow Native**: Fully integrated with Workflow SDK for production-grade reliability
 - **AI SDK Parity**: Supports the same options as AI SDK's `streamText` including generation settings, callbacks, and structured output
 
 ## Good to Know

package/docs/api-reference/workflow-globals.mdx

@@ -0,0 +1,102 @@
+---
+title: Workflow Globals
+description: Global APIs available inside workflow functions.
+type: reference
+summary: Reference of all global APIs available inside workflow functions.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/errors/node-js-module-in-workflow
+  - /docs/errors/fetch-in-workflow
+  - /docs/errors/timeout-in-workflow
+  - /docs/how-it-works/code-transform
+---
+
+Workflow functions run in a restricted environment that prevents access to non-deterministic or side-effecting APIs. This page lists all global APIs available inside `"use workflow"` functions.
+
+For full Node.js runtime access, use [step functions](/docs/foundations/workflows-and-steps#step-functions).
+
+## Deterministic APIs
+
+These APIs are available but are **seeded or fixed** to ensure deterministic behavior across replays.
+
+| API | Behavior |
+|-----|----------|
+| [`Math.random()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/random) | Seeded random number generator — same seed produces the same sequence every replay |
+| [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) / `Date.now()` / `new Date()` | Returns a fixed timestamp that advances with the workflow's logical clock |
+| [`crypto.getRandomValues()`](https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues) | Seeded — produces deterministic output for a given workflow run |
+| [`crypto.randomUUID()`](https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID) | Seeded — produces deterministic UUIDs for a given workflow run |
+| [`crypto.subtle.digest()`](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest) | Passes through to the real implementation (SHA-256, etc. are deterministic by nature) |
+
+<Callout type="info">
+You can safely use `Math.random()`, `Date.now()`, and `crypto.randomUUID()` in workflow functions. The framework ensures these return the same values across replays.
+</Callout>
+
+## Web Platform APIs
+
+These standard Web APIs are available in workflow functions:
+
+- [`Headers`](https://developer.mozilla.org/en-US/docs/Web/API/Headers)
+- [`TextEncoder`](https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder) / [`TextDecoder`](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder)
+- [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) / [`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams)
+- [`Request`](https://developer.mozilla.org/en-US/docs/Web/API/Request) / [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) — custom implementations with [special behavior in the workflow context](/docs/foundations/serialization#request--response). Body methods like `.json()` and `.text()` are automatically treated as step invocations.
+- [`console`](https://developer.mozilla.org/en-US/docs/Web/API/console)
+- [`structuredClone`](https://developer.mozilla.org/en-US/docs/Web/API/Window/structuredClone)
+- [`atob`](https://developer.mozilla.org/en-US/docs/Web/API/Window/atob) / [`btoa`](https://developer.mozilla.org/en-US/docs/Web/API/Window/btoa)
+
+## Environment Variables
+
+`process.env` is available as a **read-only, frozen** snapshot of the environment variables at the time the workflow was started. You cannot modify it.
+
+```typescript
+export async function myWorkflow() {
+  "use workflow";
+
+  const apiKey = process.env.API_KEY; // works
+  process.env.FOO = "bar"; // throws — process.env is frozen
+}
+```
+
+## Binary Data
+
+Standard JavaScript typed arrays (`Uint8Array`, `Int32Array`, `Float64Array`, etc.) are available in workflow functions.
+
+### Base64 and hex encoding
+
+The workflow environment provides [`Uint8Array` base64 and hex methods](https://tc39.es/proposal-arraybuffer-base64/) for encoding and decoding binary data:
+
+{/* @skip-typecheck: polyfilled methods not available in host TypeScript */}
+```typescript
+// Encode to base64
+const bytes = new Uint8Array([72, 101, 108, 108, 111]);
+bytes.toBase64(); // "SGVsbG8="
+bytes.toBase64({ alphabet: "base64url" }); // URL-safe variant
+bytes.toBase64({ omitPadding: true }); // "SGVsbG8"
+
+// Decode from base64
+Uint8Array.fromBase64("SGVsbG8="); // Uint8Array([72, 101, 108, 108, 111])
+
+// Encode to hex
+bytes.toHex(); // "48656c6c6f"
+
+// Decode from hex
+Uint8Array.fromHex("48656c6c6f"); // Uint8Array([72, 101, 108, 108, 111])
+
+// Write into an existing array
+const target = new Uint8Array(5);
+target.setFromBase64("SGVsbG8="); // { read: 8, written: 5 }
+target.setFromHex("48656c6c6f"); // { read: 10, written: 5 }
+```
+
+<Callout type="info">
+These methods are polyfilled in the workflow environment. When the JavaScript runtime ships native support, the polyfill is automatically bypassed.
+</Callout>
+
+## Not Available
+
+The following are **not available** in workflow functions. Move this logic to [step functions](/docs/foundations/workflows-and-steps#step-functions) instead.
+
+- **Node.js core modules**: `fs`, `path`, `http`, `https`, `net`, `dns`, `child_process`, `cluster`, `os`, `stream`, `crypto` (Node.js version), etc. See [node-js-module-in-workflow](/docs/errors/node-js-module-in-workflow).
+- **Global `fetch`**: Use [`import { fetch } from "workflow"`](/docs/api-reference/workflow/fetch) instead. See [fetch-in-workflow](/docs/errors/fetch-in-workflow).
+- **Timers**: `setTimeout`, `setInterval`, `setImmediate`, and their `clear*` counterparts. Use [`sleep()`](/docs/api-reference/workflow/sleep) instead. See [timeout-in-workflow](/docs/errors/timeout-in-workflow).
+- **`Buffer`**: Node.js-specific API. Use `Uint8Array` with `toBase64()` / `fromBase64()` / `toHex()` / `fromHex()` for binary data encoding, or `atob()` / `btoa()` for string-based base64.

package/docs/api-reference/workflow-next/index.mdx

@@ -7,7 +7,7 @@ related:
   - /docs/getting-started/next
 ---
 
-Next.js integration for Workflow DevKit that automatically configures bundling and runtime support.
+Next.js integration for Workflow SDK that automatically configures bundling and runtime support.
 
 ## Functions
 

package/docs/api-reference/workflow-serde/index.mdx

@@ -2,7 +2,7 @@
 title: "@workflow/serde"
 ---
 
-Serialization symbols for custom class serialization in Workflow DevKit.
+Serialization symbols for custom class serialization in Workflow SDK.
 
 ## Installation
 
@@ -12,7 +12,7 @@ npm i @workflow/serde
 
 ## Overview
 
-By default, Workflow DevKit can serialize standard JavaScript types like primitives, objects, arrays, `Date`, `Map`, `Set`, and more. However, custom class instances are not serializable by default because the serialization system doesn't know how to reconstruct them.
+By default, Workflow SDK can serialize standard JavaScript types like primitives, objects, arrays, `Date`, `Map`, `Set`, and more. However, custom class instances are not serializable by default because the serialization system doesn't know how to reconstruct them.
 
 The `@workflow/serde` package provides two symbols that allow you to define custom serialization and deserialization logic for your classes, enabling them to be passed between workflow and step functions.
 

package/docs/changelog/index.mdx

@@ -1,12 +1,12 @@
 ---
 title: Changelog
-description: Latest updates and new features in Workflow DevKit.
+description: Latest updates and new features in Workflow SDK.
 type: overview
 ---
 
 # Changelog
 
-Stay up to date with the latest changes to Workflow DevKit.
+Stay up to date with the latest changes to Workflow SDK.
 
 ---
 

package/docs/deploying/building-a-world.mdx

@@ -214,7 +214,7 @@ Study these implementations for guidance:
 
 ## Testing Your World
 
-Workflow DevKit includes an E2E test suite that validates World implementations. Once your World is published to npm:
+Workflow SDK includes an E2E test suite that validates World implementations. Once your World is published to npm:
 
 1. Add your world to [`worlds-manifest.json`](https://github.com/vercel/workflow/blob/main/worlds-manifest.json)
 2. Open a PR to the Workflow repository

package/docs/deploying/world/postgres-world.mdx

@@ -160,6 +160,12 @@ Prefix for graphile-worker queue job names. Useful when sharing a database betwe
 
 Number of concurrent workers polling for jobs. Default: `10`
 
+### `WORKFLOW_POSTGRES_MAX_POOL_SIZE`
+
+Maximum size of the internal `pg.Pool` used when `createWorld()` constructs the pool. Default: `10`
+
+For higher worker concurrency, Graphile Worker recommends setting `maxPoolSize` to `10` or `queueConcurrency + 2`, whichever is larger.
+
 ### Programmatic configuration
 
 {/* @skip-typecheck: incomplete code sample */}
@@ -170,6 +176,7 @@ const world = createWorld({
   connectionString: "postgres://user:password@host:5432/database",
   jobPrefix: "myapp_",
   queueConcurrency: 20,
+  maxPoolSize: 20, // overrides WORKFLOW_POSTGRES_MAX_POOL_SIZE
 });
 ```
 

package/docs/deploying/world/vercel-world.mdx

@@ -23,8 +23,6 @@ Deploy your application to Vercel:
 vercel deploy
 ```
 
-<FluidComputeCallout />
-
 That's it. Vercel automatically:
 
 - Selects the Vercel World backend
@@ -32,6 +30,24 @@ That's it. Vercel automatically:
 - Provisions storage and queuing infrastructure
 - Isolates data per environment (production, preview, development)
 
+<FluidComputeCallout />
+
+## Vercel platform documentation
+
+For complete details on pricing, usage limits, and included allotments on Vercel, see the official Vercel documentation:
+
+- **[Vercel Workflow](https://vercel.com/docs/workflow)** — Pricing details, concepts, and observability for Workflow on Vercel
+- **[Vercel limits](https://vercel.com/docs/limits)** — Platform-wide limits including Workflow-specific constraints
+- **[Vercel Hobby plan](https://vercel.com/docs/plans/hobby)** — Free tier included usage for Workflow and other resources
+
+For self-hosted deployments, use the [Postgres World](/worlds/postgres). For local development, use the [Local World](/worlds/local).
+
+## Limitations
+
+- **Single-region deployment** - The backend infrastructure is currently deployed only in `iad1`. Applications in other regions will route workflow requests to `iad1`, which may result in higher latency. For best performance, deploy your Vercel apps using Workflow to `iad1`. Global deployment is planned to colocate the backend closer to your applications.
+
+- **Data residency** - The Vercel World is currently deployed in the `iad1` region. This means independently of the deployment location of your application, the data for your workflows will be stored in the `iad1` region.
+
 ## Observability
 
 Workflow observability is built into the Vercel dashboard on your project page. It respects your existing authentication and project permission settings.
@@ -97,7 +113,8 @@ Custom base URL for the Vercel workflow API. Automatically detected.
 
 ### Programmatic configuration
 
-{/* @skip-typecheck: incomplete code sample */}
+{/*@skip-typecheck: incomplete code sample*/}
+
 ```typescript title="workflow.config.ts" lineNumbers
 import { createVercelWorld } from "@workflow/world-vercel";
 
@@ -131,13 +148,3 @@ The Vercel World uses Vercel's infrastructure for workflow execution:
 - **Authentication** - OIDC tokens provide secure, automatic authentication
 
 For more details, see the [Vercel Workflow documentation](https://vercel.com/docs/workflow).
-
-## Pricing and More
-
-See the [Vercel Workflow documentation](https://vercel.com/docs/workflow) for current pricing and to learn more.
-
-For self-hosted deployments, use the [Postgres World](/worlds/postgres). For local development, use the [Local World](/worlds/local).
-
-## Limitations
-
-- **Single-region deployment** - The backend infrastructure is currently deployed only in `iad1`. Applications in other regions will route workflow requests to `iad1`, which may result in higher latency. For best performance, deploy your Vercel apps using Workflow to `iad1`. Global deployment is planned to colocate the backend closer to your applications.

package/docs/errors/index.mdx

@@ -7,7 +7,7 @@ related:
   - /docs/foundations/errors-and-retries
 ---
 
-Fix common mistakes when creating and executing workflows in the **Workflow DevKit**.
+Fix common mistakes when creating and executing workflows in the **Workflow SDK**.
 
 <Cards>
     <Card href="/docs/errors/fetch-in-workflow" title="fetch-in-workflow">

package/docs/errors/node-js-module-in-workflow.mdx

@@ -76,5 +76,5 @@ These common Node.js core modules cannot be used in workflow functions:
 - Streams: `stream` (use Web Streams API instead)
 
 <Callout type="info">
-You can use Web Platform APIs in workflow functions (like `Headers`, `crypto.randomUUID()`, `Response`, etc.), since these are available in the sandboxed environment.
+You can use Web Platform APIs in workflow functions (like `Headers`, `crypto.randomUUID()`, `Response`, etc.), since these are available in the sandboxed environment. See [Workflow Globals](/docs/api-reference/workflow-globals) for the full list.
 </Callout>

package/docs/errors/serialization-failed.mdx

@@ -109,7 +109,7 @@ async function greetStep(userData: { name: string }) {
 
 ## Supported Serializable Types
 
-Workflow DevKit supports these types across execution boundaries:
+Workflow SDK supports these types across execution boundaries:
 
 ### Standard JSON Types
 

package/docs/errors/start-invalid-workflow-function.mdx

@@ -9,18 +9,18 @@ related:
   - /docs/api-reference/workflow-api/start
 ---
 
-This error occurs when you try to call `start()` with a function that is not a valid workflow function or when the Workflow DevKit is not configured correctly.
+This error occurs when you try to call `start()` with a function that is not a valid workflow function or when the Workflow SDK is not configured correctly.
 
 ## Error Message
 
 ```
-'start' received an invalid workflow function. Ensure the Workflow DevKit
+'start' received an invalid workflow function. Ensure the Workflow SDK
 is configured correctly and the function includes a 'use workflow' directive.
 ```
 
 ## Why This Happens
 
-The `start()` function expects a workflow function that has been properly processed by Workflow DevKit's build system. During the build process, workflow functions are transformed and marked with special metadata that `start()` uses to identify and execute them.
+The `start()` function expects a workflow function that has been properly processed by Workflow SDK's build system. During the build process, workflow functions are transformed and marked with special metadata that `start()` uses to identify and execute them.
 
 This error typically happens when:
 

package/docs/foundations/errors-and-retries.mdx

@@ -10,7 +10,7 @@ related:
   - /docs/api-reference/workflow/retryable-error
 ---
 
-By default, errors thrown inside steps are retried. Additionally, Workflow DevKit provides two new types of errors you can use to customize retries.
+By default, errors thrown inside steps are retried. Additionally, Workflow SDK provides two new types of errors you can use to customize retries.
 
 ## Default Retrying
 

package/docs/foundations/hooks.mdx

@@ -219,7 +219,7 @@ While hooks are powerful, they require you to manually handle HTTP requests and
 2. Provides an automatically addressable `url` property pointing to the generated webhook endpoint
 3. Handles sending HTTP [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) objects back to the caller
 
-When using Workflow DevKit, webhooks are automatically wired up at `/.well-known/workflow/v1/webhook/:token` without any additional setup.
+When using Workflow SDK, webhooks are automatically wired up at `/.well-known/workflow/v1/webhook/:token` without any additional setup.
 
 <Callout type="info">
 See the full API reference for [`createWebhook()`](/docs/api-reference/workflow/create-webhook) for all available options.

package/docs/foundations/serialization.mdx

@@ -9,7 +9,7 @@ related:
   - /docs/errors/serialization-failed
 ---
 
-All function arguments and return values passed between workflow and step functions must be serializable. Workflow DevKit uses a custom serialization system built on top of [devalue](https://github.com/sveltejs/devalue). This system supports standard JSON types, as well as a few additional popular Web API types.
+All function arguments and return values passed between workflow and step functions must be serializable. Workflow SDK uses a custom serialization system built on top of [devalue](https://github.com/sveltejs/devalue). This system supports standard JSON types, as well as a few additional popular Web API types.
 
 <Callout type="info">
 The serialization system ensures that all data persists correctly across workflow suspensions and resumptions, enabling durable execution.
@@ -98,7 +98,7 @@ export async function handleWebhookWorkflow() {
 
 ### Using `fetch` in Workflows
 
-Because `Request` and `Response` are serializable, Workflow DevKit provides a `fetch` function that can be used directly in workflow functions:
+Because `Request` and `Response` are serializable, Workflow SDK provides a `fetch` function that can be used directly in workflow functions:
 
 ```typescript title="workflows/api-call.ts" lineNumbers
 import { fetch } from "workflow"; // [!code highlight]

package/docs/foundations/streaming.mdx

@@ -105,7 +105,7 @@ Because streams are live and continue receiving chunks, negative `startIndex` va
 
 ## Streams as Data Types
 
-[`ReadableStream`](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) and [`WritableStream`](https://developer.mozilla.org/en-US/docs/Web/API/WritableStream) are standard Web Streams API types that Workflow DevKit makes serializable. These are not custom types - they follow the web standard - but Workflow DevKit adds the ability to pass them between functions while maintaining their streaming capabilities.
+[`ReadableStream`](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) and [`WritableStream`](https://developer.mozilla.org/en-US/docs/Web/API/WritableStream) are standard Web Streams API types that Workflow SDK makes serializable. These are not custom types - they follow the web standard - but Workflow SDK adds the ability to pass them between functions while maintaining their streaming capabilities.
 
 Unlike regular values that are fully serialized to the [event log](/docs/how-it-works/event-sourcing), streams maintain their streaming capabilities when passed between functions.
 
@@ -117,7 +117,7 @@ Unlike regular values that are fully serialized to the [event log](/docs/how-it-
 <Callout type="info">
 **How Streams Persist Across Workflow Suspensions**
 
-Streams in Workflow DevKit are backed by persistent, resumable storage provided by the "world" implementation. This is what enables streams to maintain their state even when workflows suspend and resume:
+Streams in Workflow SDK are backed by persistent, resumable storage provided by the "world" implementation. This is what enables streams to maintain their state even when workflows suspend and resume:
 
 - **Vercel deployments**: Streams are backed by a performant Redis-based stream
 - **Local development**: Stream chunks are stored in the filesystem

package/docs/foundations/workflows-and-steps.mdx

@@ -43,7 +43,7 @@ export async function processOrderWorkflow(orderId: string) {
 
 **Key Characteristics:**
 
-- Runs in a sandboxed environment without full Node.js access
+- Runs in a sandboxed environment without full Node.js access (see [Workflow Globals](/docs/api-reference/workflow-globals) for what's available)
 - All step results are persisted to the [event log](/docs/how-it-works/event-sourcing)
 - Must be **deterministic** to allow resuming after failures
 
@@ -203,5 +203,5 @@ While you can organize workflow and step functions however you like, we find tha
 You can choose to organize your steps into a single `steps.ts` file or separate files within a `steps` folder. The `shared` folder is a good place to put common steps that are used by multiple workflows.
 
 <Callout type="info">
-Splitting up steps and workflows will also help avoid most bundler related bugs with the Workflow DevKit.
+Splitting up steps and workflows will also help avoid most bundler related bugs with the Workflow SDK.
 </Callout>