Blaze

v0.17.1 : Update notes (2026/09/10)

Thank you for using Blaze!

v0.17.1 focuses on corporate-network connection diagnostics, subagents and GitHub Skill installs, and stronger Salesforce post-deploy checks, along with Salesforce workflow, file handling, and UI improvements.


1. Clearer messages for network connection errors

When login or AI features can’t connect because of a corporate proxy or firewall, Blaze now shows a dedicated explanation and next steps for each cause.

  • The connection was interrupted by network traffic inspection
  • The connection is blocked by a corporate proxy or firewall
  • The destination could not be reached

Each case comes with guidance on what to ask your IT department. We also added a “Copy diagnostics” button so you can share the details directly when contacting IT. See Network Requirements for details.

  • Login failures are also classified when they involve proxy authentication, certificates, DNS, or timeouts.
  • Blaze now uses the network route configured by your operating system, improving connectivity in corporate proxy environments.

2. Refreshed the Skills detail design

Removed the colored badges from the expanded detail view in Settings > Skills, replacing them with a simpler typography-based hierarchy.


3. Fixed the onboarding shortcut display

“Shift Tab” used to look like a single word badge, making it unclear that it’s a two-key shortcut. It’s now shown as separate “Shift” and “Tab” keycaps connected by a ”+”.


4. Made Change Management easier to use

  • Moved the “Restore this version” button to the top of the expanded history entry, where it’s easier to reach.
  • Sped up the deploy-completion check when reverting.
  • Unified the scroll behavior of error messages shown during restore.

5. You can now access log files from Settings > Files

Added a dedicated folder to the “Files” list in Settings that shows Blaze’s log files.

  • Click a file to preview its contents, or use “Show in folder” to open it in Explorer/Finder (editing and deleting are not available).
  • Makes it easier to find log files when reporting an issue to support.

6. Stability improvements

  • Reworked the connection handling for AI responses so a timed-out connection is retried automatically.

7. Complex work can now be delegated to subagents

In Flex Mode, Blaze’s AI can delegate part of a request to another AI instance so that investigation and implementation can be split up. Subagent progress and logs appear in the conversation timeline just like any other tool execution. See Subagents for details.

  • If OpenAI Codex or Claude Code is installed on your computer, you can explicitly ask Blaze to delegate work to an external AI agent.
  • Operations that affect your organization still require the same confirmation as a normal conversation. Blaze also asks for confirmation before running an external agent.

8. You can now add Skills from GitHub

Enter a GitHub repository URL under Settings > Skills > Add, or run /skill-install https://github.com/owner/repository in a conversation to add Skills from the repository to Blaze.

  • If a repository contains multiple Skills, Blaze can add them together. When multiple candidates are found and Blaze cannot determine the intended target automatically, you can choose which Skill to add in Settings.
  • When a Skill name already exists, you can skip it, replace it safely, or add it under a different name.
  • If the repository contains executable files, hooks, or symbolic links, Blaze shows what needs review before installation.
  • ZIP imports now support multiple Skills as well, with checks for unsafe paths and oversized files before installation.

9. Salesforce post-deploy checks are automatic and easier to review

After Salesforce metadata is deployed, Blaze now checks the state of the connected org automatically and returns the result to the AI.

  • It checks field and object permissions, permission set assignments, Flow activation, and Apex class/trigger status together.
  • Multiple checks run in a batch, and repeated connections to the same org are reduced, making post-deploy verification faster.
  • Because the result is available to the AI, it is less likely to repeat the same query or unnecessarily redeploy based only on a verification message.

10. Salesforce metadata operations are clearer

  • When multiple metadata items are created together, the conversation timeline now shows one operation with a list of the created targets.
  • When creating a picklist, you can specify whether values are restricted and whether they should be sorted.

11. Smoother hover feedback across lists

In lists such as model, organization, Skill, and conversation lists, the highlight now follows the item nearest to the cursor smoothly. This makes the current target easier to see and the interface feel more responsive.


12. Expanded Salesforce guidance for the AI

  • The AI can now guide you through Lightning email template creation, delivery through Apex or List Email, and open/click tracking.
  • When a Salesforce deployment error occurs, the AI can point to the relevant troubleshooting guidance and account for edge cases in field and permission settings.
  • Large guides are split into focused sections so their procedures are less likely to be cut off midway.

13. Bug fixes

  • Fixed an issue that could prevent files from being opened or managed in Settings on Windows NTFS volumes with large file identifiers.
  • Fixed an issue where a successful Salesforce deployment could be treated as failed because of a separate post-deploy observation.
  • Fixed an issue where some Salesforce commands failed to recognize an organization name when it was quoted.