v0.15.1 : Update notes (2026/08/27)
💡 Thank you for using Blaze!
v0.15.1 improves stability on Windows and the safety of Salesforce metadata edits.
1. Strengthened stability of the Windows app
- Fixed an issue where stopping a command or hitting a command timeout could restart the app and lose the conversation.
- Reworked cleanup after a stopped command so unnecessary processes no longer linger in the background.
2. Made Salesforce metadata edits safer
- Before editing existing metadata, Blaze now retrieves and verifies the latest state from the target org.
- Local files and previously retrieved results are no longer treated as the org’s current state, which prevents overwriting the org with outdated content.
- When local changes have not been applied to the org, Blaze no longer overwrites them: it shows the differences and asks you first.
3. Improved error messages and issue detection
- Fixed an issue where an MCP server initialization failure was incorrectly shown as “Please log in.” The message now explains the actual cause.
- Added diagnostics that make it possible to identify why a request stalls after you send it (no personal information is included).
- Fixed an issue where error detection could stop working in distributed builds, and made it possible to track occurrences per version.
4. Other improvements
- Fixed an issue where part of the information in Sonnet 5 responses could be lost.
- PDF and Word exports of requirements documents now render diagrams entirely inside the app, without connecting to an external site.
- Fixed the margin settings used when exporting Canvas content to PDF.
- Strengthened security.