v0.23.0 : Update notes (2026/11/08)
Thank you for using Blaze!
v0.23.0 lets you visually compare differences with your Salesforce org, and start Change Management by connecting to a team Git repository. It also adds support for Login As during browser tests, autonomous skill execution, and a beta connection to Marketing Cloud Engagement.
1. Visually compare differences with your Salesforce org
Changes found by Check differences with Salesforce in Change Management now appear in a new comparison screen. Compare your local implementation with the Salesforce org and choose what to keep.
- Filter metadata: Quickly locate changes by filtering by object name, metadata type, or file name.
- Select in bulk: For changes matching your filter, choose whether to keep your local changes or apply Salesforce changes across multiple items at once.
- Apply only selected changes: Files you leave unselected remain untouched, allowing you to import only the differences you choose.
- Review retrieval failures: View an organized list of metadata that could not be retrieved from Salesforce.
In the Change Management panel, click Check differences with Salesforce, then click the change count link to open the comparison screen. Select the desired items and click Bring in at the bottom.
This comparison covers metadata that exists both locally and in Salesforce and was successfully retrieved. Metadata that exists on only one side is not offered as an addition or deletion to apply.
This operation brings changes from Salesforce into your local workspace. It does not modify settings in your Salesforce org.
See Check differences with Salesforce.
2. Start Change Management by connecting to a team Git repository
When starting Change Management, you can now use Connect a repository to connect to your team’s Git repository and branch, beginning your work already synchronized with the team.
Sign in to GitHub to select an available repository, or enter a repository URL directly. If the branch content differs from your local files, you can review and resolve differences in the comparison screen.
You can still start Change Management locally as before.
See Connect to a team repository.
3. Support for Login As during browser tests
Browser tests can now use Salesforce’s standard Login As feature to test the interface as a specified user. This helps you verify permissions, field-level security, and layouts for different user profiles.
Turn on Allow Login As during browser tests in Settings. In browser test mode, specify the user and the actions to verify. Salesforce must also be configured to allow Login As for that user.
The browser displays the Test user, and clicking Return to admin switches back to the original administrator. Saved tests record user switches and replay them automatically during execution.
See Test Salesforce screens as another user.
4. Automatic skill execution is now supported
In Settings → Skills, turn on Allow Blaze to use skills autonomously to let Blaze automatically select and execute installed skills based on prompt instructions. This setting is off by default.
When creating a skill, fill in Description to clearly state what it does and when it should be used. Skills without descriptions are excluded from autonomous selection. Having many active skills may increase credit consumption.
We also added built-in skills to help inventory Salesforce metadata, compare metadata member lists between orgs, and review architecture across Apex, Flow, LWC, and other metadata.
See Skills.
5. Connect to Marketing Cloud Engagement (Beta)
You can now connect Marketing Cloud Engagement from Settings → Connections.
Paste the MCP URL provided by your administrator and click Sign in with browser to connect. Your administrator must configure Marketing Cloud Engagement first.
See Connect Marketing Cloud Engagement.
6. Other improvements and bug fixes
- More efficient browser operations: Reduced repeated screen checks and improved consecutive form entry and selection.
- Improved lookup selection: Lookup candidates can be matched by their primary name even when additional details are shown, and are selected automatically when exactly one candidate matches.
- Easier follow-up messages during tasks: The send button now appears whenever text is entered in the input, making it clearer that you can provide additional instructions while Blaze is working.
- Configurable queue delivery timing: Under Queue delivery timing in Settings, choose between “Steer” and “Queue messages”. You can send follow-up messages at the next break in the current task or after the current task finishes.
- More reliable queued messages: Improved persistence and message delivery order when sending multiple messages in rapid succession.
- Stable conversation selection: Background saves and incoming responses no longer unexpectedly switch the currently active conversation.
- Improved org picker and conversation lists: The org dropdown now groups orgs by environment type. When the conversation list contains only one org, it initially displays 20 conversations.
- Pre-revert org verification: Blaze checks the org again right before executing a revert and warns you if changes occurred after opening the confirmation modal.
- Enhanced revert support and recovery: Reverting now supports deleting added Bots, and recovery processes better restore approval processes to an active state after an interrupted revert.
- Clearer pre-validation errors: Error details are categorized by type, and individual Apex test and code coverage failures can be inspected separately.
- Seamless re-authentication for external apps: Updated credentials are applied immediately without having to restart the conversation.
- UI and visual refinements: Standardized menus, dialogs, and tooltips, and adjusted success, error, and warning palette contrast in the light theme.
- Device Management display fix: Resolved an issue where multiple devices were incorrectly labeled as “This device” and refined list loading states.