Peter Wielander
8d9081bacb
#3779 fixed the app migration skill, whose description ended with `mode: 'client'`. The colon-space made the plain scalar parse as a nested mapping, and the skills CLI dropped the file: `Found 5 skills`, and `--skill migrating-workflow-v4-to-v5` answered `No matching skills found`, which is the command whats-new.mdx tells readers to run. The World skill's description has no colon-space today, so it parses. It is also 590 characters of backticked identifiers, and any future edit naming a field with its value reintroduces the break. Fold it the same way now, while the value is known good. Verified with the yaml package that the folded scalar is byte-identical, and with `skills add . --skill migrating-world-v4-to-v5` that the CLI still finds all six. Signed-off-by: Peter Wielander <peter.wielander@vercel.com>
Workflow SDK
Workflow SDK makes TypeScript and JavaScript functions durable. It persists workflow progress, retries failed steps, and provides built-in observability. Workflows can suspend without using compute while they wait.
Quick start
Install the SDK in an existing project:
npm install workflow
Configure the integration for your framework. For example, with Next.js:
// next.config.ts
import { withWorkflow } from 'workflow/next';
export default withWorkflow({});
Then start a workflow from an API route, Server Action, or other server-side code:
import { start } from 'workflow/api';
import { onboardUser } from './workflows/onboard-user';
await start(onboardUser, ['hello@example.com']);
Run your app, then open the local observability UI in another terminal:
npm run dev
npx workflow web
Choose your framework in the getting-started guides.
Note
The
workflowpackage includes its full documentation, so coding agents can read version-matched guides locally fromnode_modules/workflow/docs.
Run anywhere
Local development uses the bundled backend with no configuration. Deploy to Vercel for managed storage, queuing, scaling, and observability. To self-host, use the Postgres backend or implement a custom World.
The Worlds page lists maintainer-curated third-party Worlds, including self-hosted and managed options. Submit your World by updating the Worlds Manifest.
Community
The Workflow SDK community lives on GitHub Discussions, where you can ask questions, share ideas, and show what you have built.
Contributing
Contributions are welcome. Use issues and discussions to collaborate with the team and wider community. By participating, you agree to our Code of Conduct.
Security
If you find a security vulnerability in Workflow SDK, disclose it responsibly instead of opening a public issue.
To participate in our Open Source Software Bug Bounty program, please email responsible.disclosure@vercel.com. We will add you to the program and provide further instructions for submitting your report.