v0.22.0 : Update notes (2026/11/01)

Thank you for using Blaze!

v0.22.0 introduces the ability to unsend and restore messages back to the input for quick editing, along with parallel execution for multiple subagents. It also delivers significant improvements to the conversation list and chat display, safer reverting in Change Management, and more reliable file editing and saving.

1. Unsend a message and return it to the input for editing

After sending a message, you can press the stop button at the bottom-right of the input before an AI reply or tool execution appears to cancel the message and return it to the input. Attachments and selected modes (Canvas or Document) are restored as well, so you can edit and resend immediately. You can also press Esc.

If an AI reply or tool execution has already appeared, you have started typing your next message, or there are queued messages, the input will not be restored and Blaze will only perform a standard task stop.

See Edit a message after sending it.

2. Multiple subagents can now work in parallel

When Blaze divides a complex task among subagents, it can now run multiple subagents concurrently. Independent investigations and tasks proceed in parallel, eliminating the need to wait sequentially and significantly speeding up completion. Blaze automatically determines when to use subagents based on your request, so no configuration changes are required.

• Background execution: Subagents can run independently in the background. Stopping the main task does not interrupt the subagents’ ongoing work.
• Save and resume progress: Progress and results are saved automatically and remain accessible even after restarting the app. If a restart interrupts a task, you can seamlessly resume it by sending a follow-up instruction.
• Seamless result handoff: Once a subagent finishes, its findings and output are automatically delivered to the main AI to continue subsequent tasks.
• Flexible stopping controls: You can stop subagents individually from their tabs, or press Esc twice in quick succession in the conversation view to open a confirmation modal for stopping all active subagents at once.

See Subagents.

3. Improved visibility in the conversation list and chat display

We have refreshed the conversation list and chat interface to enhance daily navigation and readability.

• Organized conversations per org: The conversation list now displays the 5 most recent conversations per Salesforce org by default, with a “Show more” option to easily expand older threads.
• Active conversations moved to the top: Sending a message automatically brings that conversation to the top of the list, making it easy to track active discussions.
• Clear visual distinction for system notices: App notices, such as task interruptions and errors, are now displayed in gray text to clearly distinguish them from AI replies.
• Real-time command output streaming: Output from running commands is now streamed and displayed progressively as it arrives.
• Fixed duplicate AI responses: Fixed an issue where stopping a task or rejecting an approval caused AI replies to be rendered twice.

4. Safer and more reliable reverting in Change Management

We have enhanced Change Management to ensure that rolling back changes to earlier versions is safer, more consistent, and clearly guided.

• Deletion of added fields and rules: Fixed an issue where individual items added to existing files (such as custom fields or sharing rules) were not properly removed from the Salesforce org during a revert.
• Consistency in partial reverts: Fixed a desync where reverting only selected fields or rules could cause discrepancies between local change history and the Salesforce org.
• Clear guidance for retained metadata: For metadata that cannot be deleted via the Salesforce Metadata API (such as translations and certain profile settings), guidance is now displayed on the relevant row of the revert confirmation screen.
• Retry interrupted reverts: If a previous revert attempt was interrupted by a network disconnect or error, you can now safely retry the process.
• Accurate validation results: Fixed an issue where outdated validation results from a different version could appear in the confirmation view.
• Automatic detection of external commits: Commits created outside Blaze (e.g., via Git CLI or VS Code) are now automatically reflected in the history without requiring a manual refresh.

See Revert to an earlier version.

5. Other improvements and bug fixes

• Parallel processing for attached images: When sending messages with only multiple images attached, image processing is now performed in parallel to reduce wait times.
• Selective MCP tool loading & state retention: For MCP (Model Context Protocol) integrations, you can now load only the tools required for your request. Selected tools are retained even after compacting conversations or restarting the app.
• File saving for long tool outputs: When summarizing lengthy tool outputs to save context, the original content is now saved to a file, allowing you to review full outputs even after app restarts or in copied threads.
• Queued message display sync: Fixed an issue where messages remained stuck in the “queued” state after subsequent messages were sent, or where the UI display desynced from the actual task execution state.
• Status updates and cleanup on errors: Change Management status is now reliably updated even when a task terminates due to an error or timeout. The app also ensures proper cleanup and error notification if issues occur during shutdown.
• Reliable file editor saving: Fixed an issue where in-progress edits or rapid consecutive saves could cause content to be lost. Also resolved an issue where files remained stuck in a loading state.
• In-app browser panel display: Opening a foreground tab in the in-app browser now automatically reveals the browser panel.
• LWC preview recovery: LWC previews can now be seamlessly restored and restarted even after the local preview server has terminated.
• Partial match skill search: You can now search for skills using partial text matching anywhere within the skill name in both the chat input and Launcher. See Skills.
• Custom org names in prompts: The custom prompt org selector now displays your assigned custom org names (aliases).
• Connection and execution stability: Improved Salesforce reconnection logic and command execution/termination handling on Windows.
• Security enhancements & software updates: Strengthened security around external service connections and in-app credential handling, and updated bundled software to the latest versions.