0.4.0

Dyad v0.4.0 introduces image and file attachments, support for LM Studio, and major debugging improvements—including accurate stack traces and smarter AI suggestions.

Highlights

Attach images/files

One of the top feature requests is here: you can now attach images and text-based files and send them to the AI. This is especially useful if you're using an existing app as inspiration for a new one.

LM Studio support

In addition to Ollama, Dyad now also supports LM Studio, making it even easier to run Dyad with local models. Thank you to pwilkin@ for contributing this. See the Local Models guide for more info.

Improved debugging

Debugging has been significantly improved in v0.4.0 with a number of changes:

• JavaScript error messages now include accurate stack traces. This addresses one of the most common complaints, where the AI would suggest clearing Vite's cache via a shell command. With accurate stack traces pointing to the correct file and line, the AI can now provide more relevant help.

• Smarter AI suggestions. The system prompt has been updated so the AI avoids suggesting shell commands, instead recommending equivalent Dyad actions like Rebuild or Restart.

• More errors are fixable with AI. Errors like invalid imports or Supabase execution failures can now be more easily resolved through AI assistance.

• No more stale error banners in preview. The preview error banner would sometimes show outdated errors from previous versions—this is now much more reliable.

• "Fix with AI" auto-submits. You no longer need to click Fix with AI and then manually submit. Clicking the button now automatically sends the chat message.

Improvements

• New Undo button. At the end of most chat messages, an Undo option lets you remove the last prompt/response pair and revert the corresponding code change. Previously, you had to use the Version list to revert.

• Retry button behavior is more intuitive. Retrying a message will now undo the code changes made by that message.

• Improved error screen when Dyad crashes. The previous brief error message has been replaced with a more helpful screen that lets you file a GitHub bug report, including relevant system information.

• Optional telemetry for app errors. When the Dyad app itself encounters an error (not your code), and telemetry is enabled, the issue is reported automatically—including crashes triggered by the new error screen. You can adjust telemetry settings anytime in the Settings page.

• Provides safety check for versioning. There were edge cases where Dyad's versioning history (git) got into a bad state. This will now show a prominent warning banner if Dyad is in this state to prompt the user to fix it.

• File editing is now under an experiment Dyad has had file editing since it launched however it has several limitations. To avoid accidental usage, we have put it behind an experiment in the Settings page. If you want to edit files in your Dyad app, we recommend using an IDE like VS Code.

• Supabase integration can be disconnected If you want to connect to a different Supabase account or org, you can now do so by disconnecting Supabase in the Settings* page.

Fixes

• Allow more file types (e.g., .md Markdown files) as codebase context
• Fixed bug where provider was incorrectly shown as set up
• Show SQL descriptions in chat message blocks
• Increased max number of versions shown from 1,000 to 10,000
• GitHub OAuth scope now includes workflow so that GitHub workflow files can be created as part of GitHub syncs.
• Chat message links open in the default browser.

What's next

Check out the Roadmap to see what's coming up.