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 →

270

Passed

Failed

Skipped

285

Total

View comprehensive E2E test results against all frameworks/configurations

1350

Passed

Failed

189

Skipped

1539

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.52s	1.43s	1.59s	15
Promise.all with 25 concurrent steps	2.94s	2.83s	3.01s	9
Promise.all with 50 concurrent steps	8.31s	8.23s	8.45s	4
Promise.race with 10 concurrent steps	1.58s	1.50s	1.67s	15
Promise.race with 25 concurrent steps	3.18s	3.01s	3.41s	8
Promise.race with 50 concurrent steps	8.85s	8.72s	9.06s	4
workflow with 1 step	1.13s	1.12s	1.14s	10
workflow with 10 sequential steps	10.93s	10.92s	10.94s	3
workflow with 25 sequential steps	27.53s	27.51s	27.55s	3
workflow with 50 sequential steps	56.75s	56.74s	56.76s	2
workflow with no steps	54ms	39ms	150ms	10

Stream Benchmarks

Benchmark	Time	TTFB	Slurp	Min	Max	Samples
workflow with stream	205ms	1.00s	12ms	197ms	221ms	10

Last updated: 3/16/2026, 9:53:28 PM · Commit: 29eb8bb

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.