Skip to content

Conversation

@VaguelySerious
Copy link
Member

@VaguelySerious VaguelySerious commented Dec 24, 2025

This PR makes it so that:

  • Running wf web in local world will open the web UI even if the configuration can't be verified
    • Other worlds will still show configuration errors if the world can't be initialized
    • We expect local world init errors mainly happens when someone is calling the web command from the wrong folder locally, or hasn't run their server yet (thus no workflow-data dir exists)
    • This also applies to wf i <command> --web and wf i web
  • The Web UI will now show a specific message when a workflow-data folder can't be found
    • It won't be treated as an error, instead showing useful info to a user
    • It will re-check the folder every three seconds
    • There's a button directing the user to change folder if they realize they got it wrong

This is separate from #626, which adds UI to remember and list past configurations, and allows re-connecting to them.

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@changeset-bot
Copy link

changeset-bot bot commented Dec 24, 2025

🦋 Changeset detected

Latest commit: 75c7cb9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@workflow/cli Patch
workflow Patch
@workflow/world-testing Patch
@workflow/ai Patch

Not sure what this means? Click here to learn what changesets are.

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

@vercel
Copy link
Contributor

vercel bot commented Dec 24, 2025

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

Project Deployment Review Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Dec 28, 2025 2:13pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Dec 28, 2025 2:13pm
example-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-astro-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-express-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-fastify-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-hono-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-nitro-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-nuxt-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workbench-vite-workflow Ready Ready Preview, Comment Dec 28, 2025 2:13pm
workflow-docs Ready Ready Preview, Comment Dec 28, 2025 2:13pm

@github-actions
Copy link
Contributor

github-actions bot commented Dec 24, 2025

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 286 0 11 297
✅ 💻 Local Development 235 0 8 243
✅ 📦 Local Production 262 0 8 270
✅ 🐘 Local Postgres 262 0 8 270
✅ 🪟 Windows 27 0 0 27
❌ 🌍 Community Worlds 109 11 0 120
Total 1181 11 35 1227

❌ Failed Tests

🌍 Community Worlds (11 failed)

mongodb (1 failed):

  • webhookWorkflow

redis (1 failed):

  • webhookWorkflow

starter (8 failed):

  • addTenWorkflow
  • addTenWorkflow
  • retryAttemptCounterWorkflow
  • crossFileErrorWorkflow - stack traces work across imported modules
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step

turso (1 failed):

  • webhookWorkflow

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 26 0 1
✅ example 26 0 1
✅ express 26 0 1
✅ fastify 26 0 1
✅ hono 26 0 1
✅ nextjs-turbopack 26 0 1
✅ nextjs-webpack 26 0 1
✅ nitro 26 0 1
✅ nuxt 26 0 1
✅ sveltekit 26 0 1
✅ vite 26 0 1
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 26 0 1
✅ express-stable 26 0 1
✅ fastify-stable 26 0 1
✅ hono-stable 26 0 1
✅ nextjs-webpack-stable 27 0 0
✅ nitro-stable 26 0 1
✅ nuxt-stable 26 0 1
✅ sveltekit-stable 26 0 1
✅ vite-stable 26 0 1
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 26 0 1
✅ express-stable 26 0 1
✅ fastify-stable 26 0 1
✅ hono-stable 26 0 1
✅ nextjs-turbopack-stable 27 0 0
✅ nextjs-webpack-stable 27 0 0
✅ nitro-stable 26 0 1
✅ nuxt-stable 26 0 1
✅ sveltekit-stable 26 0 1
✅ vite-stable 26 0 1
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 26 0 1
✅ express-stable 26 0 1
✅ fastify-stable 26 0 1
✅ hono-stable 26 0 1
✅ nextjs-turbopack-stable 27 0 0
✅ nextjs-webpack-stable 27 0 0
✅ nitro-stable 26 0 1
✅ nuxt-stable 26 0 1
✅ sveltekit-stable 26 0 1
✅ vite-stable 26 0 1
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 26 1 0
✅ redis-dev 3 0 0
❌ redis 26 1 0
✅ starter-dev 3 0 0
❌ starter 19 8 0
✅ turso-dev 3 0 0
❌ turso 26 1 0

📋 View full workflow run


Some E2E test jobs failed:

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

Check the workflow run for details.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 24, 2025

📊 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
🌐 Starter 🥇 Next.js (Turbopack) 0.038s (+4.4%) 1.015s (~) 0.977s 10 1.00x
💻 Local Next.js (Turbopack) 0.039s (+2.4%) 1.018s (~) 0.979s 10 1.03x
🌐 Redis Next.js (Turbopack) 0.039s (-2.7%) 1.017s (~) 0.977s 10 1.04x
💻 Local Nitro 0.041s (-4.4%) 1.006s (~) 0.965s 10 1.10x
💻 Local Express 0.047s (+8.0% 🔺) 1.009s (~) 0.962s 10 1.25x
🌐 Turso Next.js (Turbopack) 0.073s (-9.0% 🟢) 1.014s (~) 0.941s 10 1.94x
🌐 MongoDB Next.js (Turbopack) 0.100s (+94.6% 🔺) 1.016s (~) 0.916s 10 2.66x
🐘 Postgres Nitro 0.277s (-7.2% 🟢) 1.029s (+1.6%) 0.752s 10 7.37x
🐘 Postgres Express 0.324s (+10.5% 🔺) 1.016s (~) 0.692s 10 8.62x
🐘 Postgres Next.js (Turbopack) 0.331s (-6.9% 🟢) 1.022s (~) 0.692s 10 8.80x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.516s (-12.0% 🟢) 1.398s (-6.1% 🟢) 0.882s 10 1.00x
▲ Vercel Express 0.540s (+9.3% 🔺) 1.467s (+6.7% 🔺) 0.927s 10 1.05x
▲ Vercel Next.js (Turbopack) 0.553s (+3.6%) 1.486s (-7.9% 🟢) 0.933s 10 1.07x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.095s (~) 2.010s (~) 0.916s 10 1.00x
🌐 Starter Next.js (Turbopack) 1.097s (+1.6%) 2.010s (~) 0.913s 10 1.00x
🌐 Redis Next.js (Turbopack) 1.098s (~) 2.012s (~) 0.913s 10 1.00x
💻 Local Nitro 1.112s (~) 2.005s (~) 0.894s 10 1.02x
💻 Local Express 1.122s (+0.8%) 2.008s (~) 0.887s 10 1.02x
🌐 Turso Next.js (Turbopack) 1.298s (+0.8%) 2.012s (~) 0.715s 10 1.19x
🌐 MongoDB Next.js (Turbopack) 1.311s (+1.4%) 2.014s (~) 0.702s 10 1.20x
🐘 Postgres Next.js (Turbopack) 1.958s (-16.1% 🟢) 2.216s (-26.5% 🟢) 0.258s 10 1.79x
🐘 Postgres Express 2.167s (~) 3.013s (~) 0.847s 10 1.98x
🐘 Postgres Nitro 2.444s (+13.4% 🔺) 3.014s (~) 0.569s 10 2.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.520s (-5.8% 🟢) 3.494s (-5.1% 🟢) 0.973s 10 1.00x
▲ Vercel Express 2.633s (-2.6%) 3.572s (-0.8%) 0.939s 10 1.04x
▲ Vercel Nitro 2.699s (+8.4% 🔺) 3.568s (-1.4%) 0.869s 10 1.07x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Starter 🥇 Next.js (Turbopack) 10.607s (~) 11.012s (~) 0.406s 5 1.00x
💻 Local Next.js (Turbopack) 10.662s (~) 11.019s (~) 0.357s 5 1.01x
🌐 Redis Next.js (Turbopack) 10.684s (~) 11.017s (~) 0.333s 5 1.01x
💻 Local Nitro 10.787s (~) 11.014s (~) 0.227s 5 1.02x
💻 Local Express 10.858s (+0.6%) 11.014s (~) 0.156s 5 1.02x
🌐 Turso Next.js (Turbopack) 12.206s (~) 13.023s (~) 0.817s 5 1.15x
🌐 MongoDB Next.js (Turbopack) 12.275s (+0.7%) 13.027s (~) 0.752s 5 1.16x
🐘 Postgres Next.js (Turbopack) 14.852s (-15.5% 🟢) 15.434s (-15.4% 🟢) 0.582s 5 1.40x
🐘 Postgres Nitro 20.303s (-0.9%) 21.041s (~) 0.738s 5 1.91x
🐘 Postgres Express 20.413s (~) 21.032s (~) 0.619s 5 1.92x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 21.500s (~) 22.248s (-1.2%) 0.748s 5 1.00x
▲ Vercel Express 21.930s (+3.1%) 22.798s (+3.8%) 0.868s 5 1.02x
▲ Vercel Nitro 23.491s (+10.7% 🔺) 23.920s (+8.7% 🔺) 0.429s 5 1.09x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.356s (-1.1%) 2.011s (~) 0.655s 15 1.00x
🌐 Starter Next.js (Turbopack) 1.369s (+2.4%) 2.008s (~) 0.639s 15 1.01x
💻 Local Next.js (Turbopack) 1.377s (-1.7%) 2.011s (~) 0.634s 15 1.02x
💻 Local Nitro 1.406s (~) 2.006s (~) 0.600s 15 1.04x
💻 Local Express 1.443s (+2.1%) 2.007s (~) 0.564s 15 1.06x
🐘 Postgres Next.js (Turbopack) 1.959s (~) 2.231s (+7.3% 🔺) 0.272s 14 1.44x
🌐 MongoDB Next.js (Turbopack) 2.121s (-1.8%) 3.016s (~) 0.895s 10 1.56x
🌐 Turso Next.js (Turbopack) 2.217s (+4.5%) 3.014s (~) 0.797s 10 1.63x
🐘 Postgres Express 2.397s (+1.1%) 3.011s (~) 0.614s 10 1.77x
🐘 Postgres Nitro 2.680s (+12.8% 🔺) 3.015s (~) 0.335s 10 1.98x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.788s (+3.8%) 3.753s (+4.1%) 0.965s 8 1.00x
▲ Vercel Nitro 2.830s (~) 3.671s (-4.4%) 0.842s 9 1.01x
▲ Vercel Next.js (Turbopack) 3.133s (+6.5% 🔺) 3.860s (-1.4%) 0.727s 8 1.12x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.154s (+5.0%) 3.127s (+7.6% 🔺) 0.973s 10 1.00x
💻 Local Nitro 2.217s (-1.3%) 3.168s (-0.7%) 0.950s 10 1.03x
💻 Local Express 2.287s (+2.1%) 3.236s (+1.7%) 0.949s 10 1.06x
🌐 Starter Next.js (Turbopack) 2.487s (+1.1%) 3.012s (~) 0.525s 10 1.15x
🌐 Redis Next.js (Turbopack) 2.488s (~) 3.014s (~) 0.526s 10 1.16x
🐘 Postgres Next.js (Turbopack) 2.530s (-5.1% 🟢) 3.023s (~) 0.493s 10 1.17x
🐘 Postgres Express 2.723s (-11.0% 🟢) 3.112s (-15.8% 🟢) 0.388s 10 1.26x
🐘 Postgres Nitro 2.956s (+1.0%) 3.114s (-6.2% 🟢) 0.159s 10 1.37x
🌐 MongoDB Next.js (Turbopack) 4.722s (+3.2%) 5.183s (~) 0.461s 6 2.19x
🌐 Turso Next.js (Turbopack) 4.770s (+3.0%) 5.184s (~) 0.414s 6 2.21x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.260s (-1.8%) 3.751s (-4.8%) 0.490s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.321s (-11.2% 🟢) 4.070s (-6.0% 🟢) 0.748s 8 1.02x
▲ Vercel Nitro 3.347s (-6.8% 🟢) 4.001s (-5.2% 🟢) 0.655s 8 1.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.378s (+1.2%) 2.010s (~) 0.632s 15 1.00x
🌐 Starter Next.js (Turbopack) 1.403s (+2.3%) 2.008s (~) 0.604s 15 1.02x
💻 Local Next.js (Turbopack) 1.406s (+2.2%) 2.011s (~) 0.605s 15 1.02x
💻 Local Nitro 1.408s (~) 2.005s (~) 0.597s 15 1.02x
💻 Local Express 1.437s (+0.6%) 2.008s (~) 0.571s 15 1.04x
🐘 Postgres Next.js (Turbopack) 1.641s (-6.6% 🟢) 2.013s (~) 0.372s 15 1.19x
🐘 Postgres Express 1.726s (-9.0% 🟢) 2.010s (-3.3%) 0.284s 15 1.25x
🐘 Postgres Nitro 2.014s (+1.8%) 2.306s (+7.0% 🔺) 0.292s 14 1.46x
🌐 MongoDB Next.js (Turbopack) 2.156s (+1.4%) 3.015s (~) 0.859s 10 1.56x
🌐 Turso Next.js (Turbopack) 2.227s (+4.9%) 3.013s (~) 0.786s 10 1.62x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.545s (-3.4%) 3.619s (+2.8%) 1.074s 9 1.00x
▲ Vercel Nitro 2.588s (-4.4%) 3.531s (-6.5% 🟢) 0.943s 9 1.02x
▲ Vercel Next.js (Turbopack) 2.795s (-0.8%) 3.640s (-6.5% 🟢) 0.845s 9 1.10x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.087s (-2.4%) 3.013s (+1.2%) 0.926s 10 1.00x
💻 Local Nitro 2.204s (-2.5%) 3.161s (-1.6%) 0.956s 10 1.06x
💻 Local Express 2.303s (-1.1%) 3.262s (~) 0.959s 10 1.10x
🌐 Redis Next.js (Turbopack) 2.474s (~) 3.012s (~) 0.538s 10 1.19x
🌐 Starter Next.js (Turbopack) 2.482s (+1.4%) 3.009s (~) 0.527s 10 1.19x
🐘 Postgres Next.js (Turbopack) 2.502s (+2.0%) 3.046s (+0.8%) 0.544s 10 1.20x
🐘 Postgres Express 2.580s (-6.0% 🟢) 3.027s (~) 0.447s 10 1.24x
🐘 Postgres Nitro 3.010s (+16.6% 🔺) 3.222s (+6.9% 🔺) 0.212s 10 1.44x
🌐 MongoDB Next.js (Turbopack) 4.755s (-0.6%) 5.187s (~) 0.432s 6 2.28x
🌐 Turso Next.js (Turbopack) 4.789s (-0.9%) 5.187s (-3.1%) 0.398s 6 2.30x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.011s (-5.9% 🟢) 3.580s (-8.0% 🟢) 0.569s 9 1.00x
▲ Vercel Express 3.119s (-3.2%) 3.737s (+1.5%) 0.619s 9 1.04x
▲ Vercel Next.js (Turbopack) 3.646s (+18.2% 🔺) 4.321s (+11.4% 🔺) 0.674s 7 1.21x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🌐 Starter 🥇 Next.js (Turbopack) 0.135s (+5.0%) 1.006s (~) 0.000s (-100.0% 🟢) 1.012s (~) 0.877s 10 1.00x
💻 Local Next.js (Turbopack) 0.142s (+0.6%) 1.003s (~) 0.016s (-3.6%) 1.027s (~) 0.885s 10 1.05x
🌐 Redis Next.js (Turbopack) 0.151s (+3.2%) 1.005s (~) 0.000s (NaN%) 1.015s (~) 0.864s 10 1.12x
💻 Local Nitro 0.175s (-0.7%) 0.995s (~) 0.017s (+18.6% 🔺) 1.026s (+0.5%) 0.851s 10 1.30x
💻 Local Express 0.187s (+5.1% 🔺) 0.992s (~) 0.015s (-5.2% 🟢) 1.022s (~) 0.835s 10 1.39x
🌐 Turso Next.js (Turbopack) 0.456s (-11.1% 🟢) 0.996s (+6.6% 🔺) 0.000s (+Infinity% 🔺) 1.014s (~) 0.558s 10 3.38x
🌐 MongoDB Next.js (Turbopack) 0.511s (-3.2%) 0.942s (+2.4%) 0.000s (+100.0% 🔺) 1.015s (~) 0.504s 10 3.80x
🐘 Postgres Next.js (Turbopack) 1.023s (-29.8% 🟢) 1.473s (-11.5% 🟢) 0.000s (+Infinity% 🔺) 1.619s (-19.7% 🟢) 0.596s 10 7.60x
🐘 Postgres Nitro 2.193s (-4.2%) 2.855s (+3.7%) 0.000s (-66.7% 🟢) 3.016s (~) 0.823s 10 16.29x
🐘 Postgres Express 2.338s (+2.5%) 2.700s (-2.3%) 0.000s (NaN%) 3.014s (~) 0.676s 10 17.37x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.608s (+2.4%) 3.217s (+4.7%) 0.171s (-63.0% 🟢) 3.843s (-2.6%) 1.235s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.672s (+3.1%) 3.143s (-1.9%) 0.477s (-64.3% 🟢) 4.032s (-19.4% 🟢) 1.359s 10 1.02x
▲ Vercel Nitro 2.715s (~) 3.115s (-2.3%) 0.282s (-18.3% 🟢) 3.864s (-3.2%) 1.149s 10 1.04x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 8/8
🐘 Postgres Next.js (Turbopack) 7/8
▲ Vercel Express 4/8
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 8/8
Next.js (Turbopack) 🌐 Starter 3/8
Nitro 💻 Local 8/8
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
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

}

// If there's a config error, set a flag so web UI shows config screen
if (configError) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The needsConfig query parameter is being set in the CLI but is never read or acted upon by the web UI, so users with missing configuration won't be prompted to fix it.

View Details
📝 Patch Details
diff --git a/packages/web/src/components/settings-dropdown.tsx b/packages/web/src/components/settings-dropdown.tsx
index e587c2d..60a8627 100644
--- a/packages/web/src/components/settings-dropdown.tsx
+++ b/packages/web/src/components/settings-dropdown.tsx
@@ -2,7 +2,7 @@
 
 import { ExternalLink, Monitor, Moon, Settings, Sun } from 'lucide-react';
 import { useTheme } from 'next-themes';
-import { useState } from 'react';
+import { useEffect, useState } from 'react';
 import { Button } from '@/components/ui/button';
 import {
   DropdownMenu,
@@ -13,6 +13,7 @@ import {
   DropdownMenuTrigger,
 } from '@/components/ui/dropdown-menu';
 import { SegmentedControl } from '@/components/ui/segmented-control';
+import { useNeedsConfigState } from '@/lib/url-state';
 import { SettingsSidebar } from './settings-sidebar';
 
 // Controlled version that doesn't show the trigger button
@@ -30,6 +31,14 @@ export function SettingsDropdown() {
   const [settingsOpen, setSettingsOpen] = useState(false);
   const { theme, setTheme } = useTheme();
   const currentTheme = theme || 'system';
+  const [needsConfig] = useNeedsConfigState();
+
+  // Auto-open settings sidebar when needsConfig is present
+  useEffect(() => {
+    if (needsConfig) {
+      setSettingsOpen(true);
+    }
+  }, [needsConfig]);
 
   return (
     <>
diff --git a/packages/web/src/components/settings-sidebar.tsx b/packages/web/src/components/settings-sidebar.tsx
index ad2eeb8..de9b537 100644
--- a/packages/web/src/components/settings-sidebar.tsx
+++ b/packages/web/src/components/settings-sidebar.tsx
@@ -21,6 +21,7 @@ import {
   type WorldConfig,
 } from '@/lib/config-world';
 import { useDataDirInfo, useWorldsAvailability } from '@/lib/hooks';
+import { useNeedsConfigState } from '@/lib/url-state';
 
 interface SettingsSidebarProps {
   open?: boolean;
@@ -33,6 +34,7 @@ export function SettingsSidebar({
 }: SettingsSidebarProps = {}) {
   const config = useQueryParamConfig();
   const updateConfig = useUpdateConfigQueryParams();
+  const [needsConfig] = useNeedsConfigState();
 
   const [internalOpen, setInternalOpen] = useState(false);
   const isOpen = controlledOpen !== undefined ? controlledOpen : internalOpen;
@@ -127,6 +129,18 @@ export function SettingsSidebar({
                 </Button>
               </div>
 
+              {needsConfig && (
+                <Alert className="mb-6 !bg-blue-500/10 !border-blue-500/30">
+                  <AlertCircle className="h-4 w-4 text-blue-600 dark:text-blue-400" />
+                  <AlertTitle className="text-blue-900 dark:text-blue-200">
+                    Configuration required
+                  </AlertTitle>
+                  <AlertDescription className="text-blue-800 dark:text-blue-300">
+                    Please configure your workflow data directory to continue.
+                  </AlertDescription>
+                </Alert>
+              )}
+
               <div className="space-y-4">
                 <div className="space-y-2">
                   <Label htmlFor="backend">Backend</Label>
diff --git a/packages/web/src/lib/url-state.ts b/packages/web/src/lib/url-state.ts
index b5d0a04..9feef34 100644
--- a/packages/web/src/lib/url-state.ts
+++ b/packages/web/src/lib/url-state.ts
@@ -9,6 +9,13 @@ export function useSidebarState() {
   return useQueryState('sidebar', parseAsString);
 }
 
+/**
+ * Hook to check if configuration is needed
+ */
+export function useNeedsConfigState() {
+  return useQueryState('needsConfig', parseAsString);
+}
+
 /**
  * Hook to manage theme state in URL
  */

Analysis

needsConfig parameter not read or handled by web UI, blocking user configuration guidance

What fails: Web UI ignores the needsConfig=1 query parameter set by the CLI when configuration is missing, preventing users from being guided to fix missing workflow-data folder

How to reproduce:

  1. Run wf web when workflow-data folder is missing
  2. CLI detects error and sets needsConfig=1 parameter in URL
  3. Web UI loads but settings sidebar does NOT automatically open
  4. User sees normal UI with no indication that configuration is needed

Result: Users must manually click "Configuration" menu to access settings. No guidance shown about missing configuration.

Expected behavior: Per PR goals:

  • Settings sidebar should auto-open when needsConfig=1 parameter is present
  • Informational message should appear guiding user to configure folder
  • This matches how other URL parameters trigger auto-navigation (e.g., runId, stepId, hookId)

Root cause:

  • CLI sets needsConfig parameter in packages/cli/src/lib/inspect/web.ts line 377
  • Web UI never reads or handles this parameter:
    • No parser in packages/web/src/lib/config.ts (only handles backend, env, authToken, project, team, port, dataDir, manifestPath)
    • No hook in packages/web/src/lib/url-state.ts
    • Not checked in packages/web/src/components/settings-dropdown.tsx

Fix implemented:

  1. Added useNeedsConfigState() hook to packages/web/src/lib/url-state.ts to read the parameter
  2. Updated SettingsDropdown to auto-open settings sidebar when needsConfig is present
  3. Updated SettingsSidebar to display informational message "Configuration required" when opened this way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants