Skip to content

docs: add AI generation pipelines guide#1108

Open
johnlindquist wants to merge 6 commits intomainfrom
docs/ai-generation
Open

docs: add AI generation pipelines guide#1108
johnlindquist wants to merge 6 commits intomainfrom
docs/ai-generation

Conversation

@johnlindquist
Copy link
Contributor

@johnlindquist johnlindquist commented Feb 18, 2026

Summary

  • Adds generation pipelines guide to the AI Agents documentation section
  • Covers batch content generation, image/media generation, multi-stage pipelines, fan-out patterns, progress streaming, and AI error handling
  • Motivated by usage data: 155 teams using AI/ML workflows but docs only cover chat-based agents

Test plan

  • Verify MDX renders correctly
  • Verify code examples are syntactically valid (all 7 code samples pass pnpm test:docs)
  • Verify meta.json navigation works
  • Link validation passes (bun run lint:links - 0 errors)

@changeset-bot
Copy link

changeset-bot bot commented Feb 18, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: 74ddd79

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Contributor

vercel bot commented Feb 18, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Feb 25, 2026 8:16pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Feb 25, 2026 8:16pm
example-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-astro-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-express-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-fastify-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-hono-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-nitro-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-nuxt-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workbench-vite-workflow Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workflow-docs Ready Ready Preview, 💬 6 unresolved, Open in v0 Feb 25, 2026 8:16pm
workflow-nest Ready Ready Preview, Comment Feb 25, 2026 8:16pm
workflow-swc-playground Ready Ready Preview, Comment Feb 25, 2026 8:16pm

@github-actions
Copy link
Contributor

github-actions bot commented Feb 18, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 523 0 49 572
✅ 💻 Local Development 556 0 68 624
✅ 📦 Local Production 556 0 68 624
❌ 🐘 Local Postgres 555 1 68 624
✅ 🪟 Windows 49 0 3 52
❌ 🌍 Community Worlds 111 45 9 165
✅ 📋 Other 135 0 21 156
Total 2485 46 286 2817

❌ Failed Tests

🐘 Local Postgres (1 failed)

vite-stable (1 failed):

  • webhookWorkflow
🌍 Community Worlds (45 failed)

turso (45 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • parallelSleepWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling retry behavior workflow completes despite transient 5xx on step_completed
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • cancelRun - cancelling a running workflow
  • cancelRun via CLI - cancelling a running workflow
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 47 0 5
✅ example 47 0 5
✅ express 47 0 5
✅ fastify 47 0 5
✅ hono 47 0 5
✅ nextjs-turbopack 50 0 2
✅ nextjs-webpack 50 0 2
✅ nitro 47 0 5
✅ nuxt 47 0 5
✅ sveltekit 47 0 5
✅ vite 47 0 5
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
✅ vite-stable 45 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
✅ vite-stable 45 0 7
❌ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 45 0 7
✅ express-stable 45 0 7
✅ fastify-stable 45 0 7
✅ hono-stable 45 0 7
✅ nextjs-turbopack-canary 49 0 3
✅ nextjs-turbopack-stable 49 0 3
✅ nextjs-webpack-canary 49 0 3
✅ nextjs-webpack-stable 49 0 3
✅ nitro-stable 45 0 7
✅ nuxt-stable 45 0 7
✅ sveltekit-stable 45 0 7
❌ vite-stable 44 1 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 49 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
✅ mongodb 49 0 3
✅ redis-dev 3 0 0
✅ redis 49 0 3
✅ turso-dev 3 0 0
❌ turso 4 45 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 45 0 7
✅ e2e-local-postgres-nest-stable 45 0 7
✅ e2e-local-prod-nest-stable 45 0 7

📋 View full workflow run

❌ Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: failure
  • Windows: success

Check the workflow run for details.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 18, 2026 •
edited
Loading

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.031s (-4.0%) 1.005s (~) 0.974s 10 1.00x
💻 Local Express 0.033s (-0.9%) 1.005s (~) 0.972s 10 1.05x
🐘 Postgres Nitro 0.053s (-6.7% 🟢) 1.010s (~) 0.957s 10 1.70x
🐘 Postgres Express 0.055s (+2.6%) 1.012s (~) 0.957s 10 1.77x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 0.524s (-7.4% 🟢) 2.285s (+14.7% 🔺) 1.761s 10 1.00x
▲ Vercel Nitro 0.668s (+25.0% 🔺) 2.338s (+28.9% 🔺) 1.670s 10 1.27x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.104s (~) 2.005s (~) 0.901s 10 1.00x
💻 Local Nitro 1.105s (~) 2.006s (~) 0.901s 10 1.00x
🐘 Postgres Nitro 1.125s (-0.8%) 2.010s (~) 0.885s 10 1.02x
🐘 Postgres Express 1.141s (~) 2.012s (~) 0.871s 10 1.03x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.259s (+15.8% 🔺) 3.465s (+17.7% 🔺) 1.206s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.391s (+22.9% 🔺) 3.438s (+11.3% 🔺) 1.048s 10 1.06x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 10.799s (~) 11.021s (~) 0.222s 3 1.00x
💻 Local Express 10.831s (~) 11.023s (~) 0.191s 3 1.00x
🐘 Postgres Nitro 10.855s (~) 11.040s (~) 0.185s 3 1.01x
🐘 Postgres Express 10.893s (~) 11.040s (~) 0.147s 3 1.01x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 16.822s (+4.0%) 18.076s (+6.1% 🔺) 1.254s 2 1.00x
▲ Vercel Nitro 17.468s (+9.3% 🔺) 19.236s (+13.7% 🔺) 1.768s 2 1.04x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 27.189s (-0.6%) 28.055s (~) 0.866s 3 1.00x
🐘 Postgres Express 27.254s (~) 28.063s (~) 0.810s 3 1.00x
💻 Local Nitro 27.445s (~) 28.050s (~) 0.605s 3 1.01x
💻 Local Express 27.516s (~) 28.052s (~) 0.536s 3 1.01x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 43.962s (+1.2%) 45.195s (+1.1%) 1.233s 2 1.00x
▲ Vercel Nitro 44.385s (+4.2%) 45.755s (+5.5% 🔺) 1.371s 2 1.01x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 55.016s (~) 55.091s (~) 0.075s 2 1.00x
🐘 Postgres Nitro 55.027s (~) 55.099s (-1.8%) 0.072s 2 1.00x
💻 Local Nitro 57.173s (~) 58.096s (~) 0.923s 2 1.04x
💻 Local Express 57.322s (~) 58.103s (~) 0.780s 2 1.04x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 94.826s (+2.2%) 95.683s (+2.6%) 0.857s 1 1.00x
▲ Vercel Next.js (Turbopack) 97.801s (-2.5%) 98.923s (-2.3%) 1.122s 1 1.03x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.364s (+0.9%) 2.010s (~) 0.646s 15 1.00x
🐘 Postgres Express 1.373s (~) 2.010s (~) 0.637s 15 1.01x
💻 Local Express 1.408s (~) 2.005s (~) 0.597s 15 1.03x
💻 Local Nitro 1.408s (-1.6%) 2.006s (~) 0.597s 15 1.03x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.383s (+7.5% 🔺) 3.479s (+10.7% 🔺) 1.095s 9 1.00x
▲ Vercel Nitro 2.519s (-1.6%) 3.576s (+2.5%) 1.057s 9 1.06x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 2.002s (+2.8%) 2.515s (~) 0.513s 12 1.00x
🐘 Postgres Express 2.016s (+3.9%) 2.514s (+1.6%) 0.498s 12 1.01x
💻 Local Nitro 2.564s (-2.0%) 3.008s (~) 0.444s 10 1.28x
💻 Local Express 2.628s (+4.1%) 3.007s (~) 0.379s 10 1.31x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.921s (-8.7% 🟢) 4.086s (-18.4% 🟢) 1.165s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.019s (-4.3%) 3.940s (-3.1%) 0.922s 8 1.03x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.552s (+3.9%) 4.269s (+5.9% 🔺) 0.717s 8 1.00x
🐘 Postgres Express 4.071s (+23.7% 🔺) 4.601s (+17.9% 🔺) 0.529s 7 1.15x
💻 Local Nitro 7.224s (-2.3%) 8.017s (~) 0.793s 4 2.03x
💻 Local Express 7.537s (~) 8.021s (~) 0.483s 4 2.12x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.052s (-5.1% 🟢) 3.995s (-14.8% 🟢) 0.943s 8 1.00x
▲ Vercel Next.js (Turbopack) 11.069s (+207.6% 🔺) 11.847s (+155.4% 🔺) 0.778s 5 3.63x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.359s (~) 2.010s (~) 0.651s 15 1.00x
🐘 Postgres Express 1.399s (+3.0%) 2.010s (~) 0.611s 15 1.03x
💻 Local Nitro 1.425s (~) 2.005s (~) 0.580s 15 1.05x
💻 Local Express 1.455s (+1.8%) 2.004s (~) 0.549s 15 1.07x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.102s (-1.7%) 3.271s (+7.8% 🔺) 1.169s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.310s (+14.2% 🔺) 3.342s (+8.9% 🔺) 1.031s 10 1.10x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.927s (-1.6%) 2.398s (-3.1%) 0.471s 13 1.00x
🐘 Postgres Express 2.014s (+0.7%) 2.514s (~) 0.500s 12 1.05x
💻 Local Nitro 2.735s (-0.6%) 3.007s (~) 0.271s 10 1.42x
💻 Local Express 2.801s (+5.0%) 3.009s (~) 0.208s 10 1.45x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.517s (+4.4%) 3.682s (+12.0% 🔺) 1.165s 9 1.00x
▲ Vercel Next.js (Turbopack) 2.967s (+17.6% 🔺) 4.092s (+22.6% 🔺) 1.124s 8 1.18x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.376s (+5.1% 🔺) 4.309s (+10.6% 🔺) 0.933s 7 1.00x
🐘 Postgres Express 3.782s (+9.7% 🔺) 4.459s (+7.5% 🔺) 0.677s 7 1.12x
💻 Local Express 8.025s (+3.2%) 8.520s (+3.0%) 0.495s 4 2.38x
💻 Local Nitro 8.187s (+4.3%) 9.018s (+5.8% 🔺) 0.831s 4 2.42x
💻 Local Next.js (Turbopack) ⚠️ missing - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.181s (-5.9% 🟢) 4.180s (-3.6%) 1.000s 8 1.00x
▲ Vercel Nitro 3.289s (+1.4%) 4.297s (+2.4%) 1.008s 7 1.03x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.169s (-4.9%) 1.002s (~) 0.011s (-2.7%) 1.016s (~) 0.848s 10 1.00x
💻 Local Express 0.175s (+1.0%) 1.002s (~) 0.011s (+5.5% 🔺) 1.017s (~) 0.842s 10 1.04x
🐘 Postgres Express 0.180s (-6.7% 🟢) 0.995s (~) 0.001s (-6.7% 🟢) 1.012s (~) 0.832s 10 1.07x
🐘 Postgres Nitro 0.185s (-5.9% 🟢) 0.991s (~) 0.001s (-29.4% 🟢) 1.011s (~) 0.826s 10 1.10x
💻 Local Next.js (Turbopack) ⚠️ missing - - - - -
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 1.535s (+8.2% 🔺) 1.692s (~) 0.188s (+65.9% 🔺) 2.330s (+6.7% 🔺) 0.795s 10 1.00x
▲ Vercel Next.js (Turbopack) 1.723s (+16.8% 🔺) 2.370s (+35.6% 🔺) 0.101s (+5.9% 🔺) 2.948s (+31.7% 🔺) 1.225s 10 1.12x
▲ Vercel Express ⚠️ missing - - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Nitro 9/12
🐘 Postgres Nitro 10/12
▲ Vercel Nitro 7/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 🐘 Postgres 8/12
Next.js (Turbopack) ▲ Vercel 12/12
Nitro 🐘 Postgres 6/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

❌ Some benchmark jobs failed:

  • Local: success
  • Postgres: success
  • Vercel: failure

Check the workflow run for details.

@johnlindquist
Merge remote-tracking branch 'origin/main' into docs/ai-generation
aa6bd98
@johnlindquist
Address PR review feedback on generation pipelines guide
a9b38d7 
- Rewrite Image and Media Generation section to use proper workflow
  patterns (webhooks + workflow-level polling) instead of polling inside
  a step
- Switch all AI model references from @workflow/ai/openai to
  @ai-sdk/gateway with gateway("openai/gpt-4o") format
- Add client-side stream consumption note for progress streaming section
- Remove accidental code highlight on Multi-Stage Pipelines import line
@johnlindquist johnlindquist requested a review from a team as a code owner February 25, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vercel vercel[bot] vercel[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@johnlindquist