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 →

326

Passed

Failed

Skipped

385

Total

View comprehensive E2E test results against all frameworks/configurations

1768

Passed

Failed

311

Skipped

2079

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.49s	1.42s	1.55s	15
Promise.all with 25 concurrent steps	3.04s	2.92s	3.15s	8
Promise.all with 50 concurrent steps	8.84s	8.44s	9.37s	4
Promise.race with 10 concurrent steps	1.54s	1.46s	1.65s	15
Promise.race with 25 concurrent steps	3.19s	2.56s	4.13s	8
Promise.race with 50 concurrent steps	9.03s	8.60s	9.47s	4
workflow with 1 step	1.13s	1.12s	1.16s	10
workflow with 10 concurrent data payload steps (10KB)	617ms	511ms	902ms	60
workflow with 10 sequential data payload steps (10KB)	976ms	949ms	1.05s	54
workflow with 10 sequential steps	10.91s	10.90s	10.92s	3
workflow with 25 concurrent data payload steps (10KB)	2.63s	2.42s	2.83s	30
workflow with 25 sequential data payload steps (10KB)	2.97s	2.89s	3.06s	27
workflow with 25 sequential steps	14.98s	14.95s	15.01s	4
workflow with 50 concurrent data payload steps (10KB)	11.60s	11.31s	11.85s	10
workflow with 50 sequential data payload steps (10KB)	9.09s	8.95s	9.29s	13
workflow with 50 sequential steps	16.62s	16.50s	16.74s	6
workflow with no steps	43ms	39ms	50ms	10

Stream Benchmarks

Benchmark	Time	TTFB	Slurp	Min	Max	Samples
10 parallel streams (1MB each)	1.30s	2.02s	0ms	1.23s	1.36s	30
fan-out fan-in 10 streams (1MB each)	3.72s	4.16s	1ms	3.38s	4.36s	15
stream pipeline with 5 transform steps (1MB)	750ms	1.01s	11ms	723ms	821ms	59
workflow with stream	203ms	1.00s	12ms	196ms	222ms	10

Last updated: 3/23/2026, 10:51:08 PM · Commit: 90ea870

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.