1.19.0

Nitro compatibility for Cloudflare Workers, AI-assisted deployment fixes, a new GitHub plugin, bring-your-own API keys for Dyad Pro, and Claude Code reliability improvements

Dyad v1.19.0 adds Nitro compatibility for Cloudflare Workers, makes failed deployments easier to troubleshoot with AI, introduces a GitHub plugin that requires no configuration, supports personal API keys with Dyad Pro, and improves Claude Code session reliability.

Highlights

Deploy Nitro apps to Cloudflare Workers (Experimental)

You can now deploy supported Nitro apps directly to Cloudflare Workers.

Dyad handles the required deployment configuration, making it easier to publish these apps from the Publish panel.

Fix failed Cloudflare deployments with AI (Experimental)

When a Cloudflare deployment fails, you can now select the Fix with AI button to investigate the error and make changes to your app.

This gives Agent mode the deployment context it needs to help diagnose and resolve the failure without manually copying error details into chat.

Cloudflare Workers publishing and AI-assisted deployment fixes are experimental. Use with caution.

GitHub plugin with no configuration required

GitHub is now available in the plugin catalog, and you can connect your account without any additional configuration.

Once connected, Agent mode can use GitHub tools to perform tasks such as opening or checking issues and pushing changes directly from chat.

Use your own API keys with Dyad Pro

Dyad Pro now supports bring-your-own API keys, letting you use personal provider credentials while retaining access to Dyad Pro features.

Custom Supabase user fixtures in E2E tests

E2E tests for Supabase apps can now use custom fixtures to create the users and prerequisite records they need, including user metadata required by signup triggers and multiple test users with explicit credentials.

If your app's signup triggers reject Dyad's automatic test user, tests now continue with your fixtures instead of failing before they run. Agent mode is also guided to inspect your database schema, auth triggers, and signup code before choosing a fixture.

Enhancements & fixes

Fixed repeated Claude Code token charges when resuming a session.
Claude Code questionnaires now remain active while waiting for responses, and abandoned tool calls are released more reliably.
Supabase edge function deployments now explain why a full redeploy of every function was needed when an incremental deployment was not possible.
App search no longer loads every matching message, improving performance for apps with large chat histories.
Bug report screenshots are now uploaded and embedded directly in the GitHub issue.