Local World | Workflow DevKit

The Local World is bundled with workflow and used automatically during local development. No installation or configuration required.

To explicitly use the local world in any environment, set the environment variable:

WORKFLOW_TARGET_WORLD=local

Observability

The workflow CLI uses the local world by default. Running these commands inside your workflow project will show your local development workflows:

# List recent workflow runs
npx workflow inspect runs

# Launch the web UI
npx workflow web

Learn more in the Observability documentation.

Testing & Performance

E2E Tests

Passing100% passing

Spec compliance is tested against Next.js (Turbopack) built in production mode and started with `next start`. View CI run →

341

Passed

Failed

Skipped

415

Total

View comprehensive E2E test results against all frameworks/configurations

1849

Passed

Failed

392

Skipped

2241

Total

Benchmarks

Click on a benchmark to view performance history over the last 30 commits.

Benchmark	Time	Min	Max	Samples
Promise.all with 10 concurrent steps	1.50s	1.42s	1.65s	15
Promise.all with 25 concurrent steps	2.98s	2.63s	3.35s	10
Promise.all with 50 concurrent steps	8.22s	8.13s	8.36s	4
Promise.race with 10 concurrent steps	1.53s	1.45s	1.63s	15
Promise.race with 25 concurrent steps	3.00s	2.47s	3.20s	9
Promise.race with 50 concurrent steps	8.81s	8.68s	8.98s	4
workflow with 1 step	1.13s	1.12s	1.15s	10
workflow with 10 concurrent data payload steps (10KB)	580ms	467ms	713ms	60
workflow with 10 sequential data payload steps (10KB)	989ms	944ms	1.09s	45
workflow with 10 sequential steps	10.93s	10.90s	10.96s	3
workflow with 25 concurrent data payload steps (10KB)	2.50s	2.33s	2.79s	30
workflow with 25 sequential data payload steps (10KB)	3.07s	2.98s	3.18s	23
workflow with 25 sequential steps	14.92s	14.90s	14.93s	4
workflow with 50 concurrent data payload steps (10KB)	11.08s	10.77s	11.52s	11
workflow with 50 sequential data payload steps (10KB)	9.11s	8.87s	9.34s	13
workflow with 50 sequential steps	16.77s	16.50s	16.95s	6
workflow with no steps	47ms	40ms	64ms	10

Stream Benchmarks

Benchmark	Time	TTFB	Slurp	Min	Max	Samples
10 parallel streams (1MB each)	1.22s	2.02s	1ms	1.17s	1.27s	30
fan-out fan-in 10 streams (1MB each)	3.54s	4.03s	1ms	3.15s	4.00s	15
stream pipeline with 5 transform steps (1MB)	715ms	1.01s	8ms	687ms	764ms	59
workflow with stream	199ms	1.00s	12ms	196ms	204ms	10

Last updated: 3/24/2026, 5:33:10 PM · Commit: a375a3f

Configuration

The local world works with zero configuration, but you can customize behavior through environment variables or programmatically via createLocalWorld().

`WORKFLOW_LOCAL_DATA_DIR`

Directory for storing workflow data as JSON files. Default: .workflow-data/

`PORT`

The application dev server port. Used to enqueue steps and workflows. Default: auto-detected

`WORKFLOW_LOCAL_BASE_URL`

Full base URL override for HTTPS or custom hostnames. Default: http://localhost:{port}

Port resolution priority: baseUrl > port > PORT > auto-detected

`WORKFLOW_LOCAL_QUEUE_CONCURRENCY`

Maximum number of concurrent queue workers. Default: 100

Programmatic configuration

workflow.config.ts

import { createLocalWorld } from "@workflow/world-local";

const world = createLocalWorld({
  dataDir: "./custom-workflow-data",
  port: 5173,
  // baseUrl overrides port if set
  baseUrl: "https://local.example.com:3000",
});

Limitations

The local world is designed for development, not production:

In-memory queue - Steps are queued in memory and do not persist across server restarts
Filesystem storage - Data is stored in local JSON files
Single instance - Cannot handle distributed deployments
No authentication - Suitable only for local development

For production deployments, use the Vercel World or Postgres World.