1.23.0 Beta 1

Dyad v1.23.0 Beta 1 adds parallel E2E test runs and helps keep Neon production data separate from development.

Highlights

Speed up E2E testing with parallel runs

Multiple E2E test runs can now happen at the same time, each in its own isolated workspace, so you don't have to wait for one run to finish before the next starts.

To enable this feature, turn on Allow parallel E2E test runs in your workflow settings. You can also set how many runs can happen at once.

Keep Neon production data separate

By default, Dyad now avoids using your production Neon branch for development or your development branch for deployment. This keeps data and schema changes made while building out of your live database.

To use any branch for development or deployment, turn off Protect Neon database branches in the experiments section.

Enhancements & fixes

• Plugins you've added in Dyad work in Claude Code more reliably.
• You can now turn off thinking when using LM Studio or custom model providers.
• Neon apps now suggest enabling E2E testing when it is not already configured.
• Prompts sent during undo or codebase restore are now queued until the operation finishes.
• Production builds now cancel and time out reliably while isolated workspaces are being prepared.
• Fixed image uploads on Windows when apps contain hidden or system Git ignore files.
• When Supabase test setup or cleanup fails, Dyad now explains how to recover.
• The GitHub collaborators panel now explains when you lack push access instead of displaying a generic 403 error.
• Google API key validation is now more reliable.
• Missing app folders now produce a clear message instead of a misleading Git error.
• Bug report log excerpts now retain warnings that may help diagnose issues.
• Removing isolated workspaces on Windows no longer follows directory junctions, preventing files outside the workspace from being deleted.

Feedback

If you run into issues or have suggestions, please help us improve by reporting a bug.