Blaze

v0.20.0 : Update notes (2026/10/17)

Thank you for using Blaze!

v0.20.0 brings manual conversation compaction, replaying, editing, and sharing saved browser tests, expanded search, and GitHub push and pull.


1. Reuse browser tests more easily

Save Salesforce browser operations and rerun them from the test details. Recorded operations are replayed without AI first; when a screen change prevents replay, Blaze handles the issue.

  • Edit values and add fields in saved test details. Inspect screens using step thumbnails.
  • Calculate values on each run, such as dates or names that differ each time.
  • Split and save operations from the same conversation as separate tests. Save partial operations as unfinished tests.
  • Organize and share tests by renaming, pinning, or archiving them. Share tests to your organization’s library so other members can add them.
  • Switch to the target org and run from the test details.
  • Ask Blaze to edit the open test’s steps or starting page in the conversation.

Toggle Browser test mode from “+” beside the input. It stays enabled when you switch conversations.

See Rerun saved tests.


2. Find settings, tests, Canvas documents, and files from the search panel

The search panel now includes settings, saved tests, Canvas documents, and files alongside conversations.

  • Find an org’s conversations by its display name, alias, or username.
  • Search conversations that have not loaded in the sidebar, and scroll down to load more results.
  • Select a test and press ⌘Enter on Mac or Ctrl+Enter on Windows to run it directly.

See Search conversations, settings, and tests.


3. Push and pull from GitHub in Change Management

Send saved changes to GitHub or bring your team’s GitHub changes onto this computer.

Use the “⋯” menu in Change Management. Push and pull do not change your Salesforce org.

When a pull finds conflicting changes, compare your changes and a teammate’s changes in Blaze and choose which to keep. Supported text changes also offer “Keep both”.

See Change Management.


4. Let Blaze operate the browser during ordinary conversations

In Settings → General → Browser, enable Allow Blaze to operate the browser so Blaze can inspect and operate pages when needed.

Even when this setting is off, Blaze can use the browser in Browser test mode.

See Built-in Browser.


5. Copy a thread as is or with a summary

From a thread’s “⋯” → “Copy thread” menu in the conversation list, choose what to carry over.

  • Copy as is: Carry over the whole conversation and continue in a separate thread.
  • Copy with summary: Carry over the key points. This is useful for splitting work across separate agents.

In a thread copied with a summary, expand “Carried-over summary” to review the context.


6. Export conversations and execution records as TXT

From the app’s File menu, choose Export current conversation or Export all conversations to save a TXT file.

Alongside conversations, you can review recorded AI requests and responses, tool operations, and their results. Information that was not recorded, including missing details from older conversations, is shown as not recorded.


7. Compact long conversations when you choose

Send /compact in the conversation input to summarize the context needed for your work and continue in the same thread. Use it at a task boundary or when a conversation grows long.

  • Specify details to preserve, for example /compact Preserve the opportunity flow requirements and outstanding checks.
  • If a summary would not make a short conversation smaller, Blaze keeps it as is.

See Compact a conversation (/compact).


8. Improvements and bug fixes

  • Grouped notifications for saves, pulls, updates, and other operations in the lower-left corner so progress and results are easier to follow.
  • Pull completion notifications now show the number of changes actually pulled.
  • Fixed the process that keeps external tools signed in when the app starts.
  • Reduced waiting time when starting replay or stopping a browser test.
  • Improved test replay inside embedded frames and handling of screen changes.
  • Improved Salesforce picklist input. If a value is not available, Blaze shows the available options.
  • Fixed browser operations stopping when you returned to the same tab.
  • Fixed Blaze moving in front of other apps during browser operations.
  • Fixed cases where custom prompt operations did not work correctly.
  • Improved the login screen and made its button easier to use.
  • Updated some app names in Connections to their official names.

Clicking a link shown in the chat opens it in a new tab of the Blaze browser.

  • You can switch to “Default browser” under “Where to open links” in the “Browser” section of the “General” tab in Settings.
  • Hold the Command key on Mac, or the Ctrl key on Windows, and click to open the link in the browser you have not selected in Settings.

For details, see Choose Which Browser Opens Links.