Blaze CLI v0.11.0 : Release notes (2026/08/29)

Thank you for using Blaze!

Here are the changes since v0.10.0. This update adds support for various Salesforce features and MCP integrations for external tools, and revises how approval mode behaves. For update commands by installation method, see Updates.

1. Support for various Salesforce features

Blaze CLI now supports various Salesforce features, including Apex, LWC, Flow, Agentforce, Data Cloud, and OmniStudio. You can use Blaze CLI more easily for questions and implementation work across these areas.

2. Use MCP server tools from Blaze

You can now configure Model Context Protocol (MCP) servers and call their tools from a Blaze conversation. Blaze starts only servers that you have reviewed and explicitly trusted.

First, check the configured server status:

blaze mcp list

After reviewing a server, trust it explicitly:

blaze mcp trust <server-name>

To list the tools exposed by a trusted server:

blaze mcp tools <server-name>

If you change a server’s command, arguments, or environment variable settings, its previous trust is invalidated. Review the new configuration and run blaze mcp trust again.

3. Approval mode now behaves more consistently and safely

With --approval-mode, normal file and read operations continue without a prompt, while destructive Salesforce commands require confirmation before they run. This lets you review operations that change an org, such as deployments and data deletion.

blaze --approval-mode

During a TUI session, press Shift + Tab to cycle through safe mode, approval mode, and trust mode. --approval-mode and --trusts-everything cannot be used together.

The approval panel shows the target org and metadata details, and masks API keys, tokens, passwords, and similar secrets before displaying a command. In --json mode, approval requests are emitted as JSON Lines and then automatically denied.

4. Improved error message display

Blaze now distinguishes between the Blaze API, BYOK endpoints, Ollama, and other local or remote servers, and displays a Japanese or English message that matches the situation.

Common causes are easier to identify, including:

• An expired Blaze login or a required re-authentication
• An incorrect BYOK API key, endpoint, or model name
• Japan-hosted model restrictions or an organization network policy
• Usage limits, rate limiting, or a temporary service outage
• Ollama or another local server not running

Error messages and diagnostics are sanitized so secrets such as API keys and ID tokens are not exposed.

5. Other improvements

• Safe-to-run read operations can be processed in parallel, making information gathering faster.
• Tool results and conversation history stay more consistent when a tool run is cancelled or a session is resumed.