Blaze CLI v0.3.2 : Release notes (2026/05/20)

Thank you for using Blaze!

1. Install via npm and Homebrew

In addition to the existing curl / PowerShell installers, you can now install Blaze CLI from your favorite package manager.

New install paths:

# npm
npm install -g @igness/blaze

# Homebrew (Apple Silicon Mac)
brew install igness-ai/tap/blaze

blaze update now detects how the running binary was installed and points you at the right upgrade command — brew upgrade blaze for Homebrew installs, npm install -g @igness/blaze@latest for npm installs. This prevents a self-update from silently overwriting a binary that your package manager still thinks it owns.

See Install and Updates for details.

2. Disconnect orgs straight from /org

Previously, removing a Salesforce org from Blaze meant dropping into a separate terminal to run sf org logout. You can now do it directly from the /org list.

How to use it:

• Open the org list with /org and move the cursor onto a connected org

• Press d to bring up a confirmation bar

• Press Enter to disconnect, or Esc / n to cancel

If you disconnect the default org, the default_org entry in your config is cleared automatically. The org itself remains in Salesforce — only the local connection is removed.

See /org for details.

3. Four lifecycle hooks

You can now extend Blaze CLI from external tools (history loggers, notifiers, custom automation, …) by registering shell commands that fire at well-defined points in the session lifecycle. Define them in ~/.blaze/settings.json:

• SessionStart — right after a Blaze session begins
• SessionEnd — right after the session ends
• PreCompact — just before /compact compresses the conversation
• Stop — right after Blaze finishes responding (both success and error)

The format is compatible with the Claude Code hooks spec. Example:

{
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          { "type": "command", "command": "echo session started >> ~/blaze.log" }
        ]
      }
    ]
  }
}

Each command receives a JSON payload on stdin including session_id, cwd, and hook_event_name. See hooks for the full guide.

4. JSON-based advanced settings for BYOK

For the BYOK endpoints you connect through the /model wizard (OpenRouter / OpenAI-compatible / Ollama), you can now hand-edit ~/.blaze/config.json under byok_overrides to control routing in detail.

Available knobs:

• provider.order — preferred provider order for each request
• provider.allow_fallbacks — whether to allow fallback to providers outside order
• reasoning.effort — low / medium / high (supported models only)

Example (pin OpenRouter to the Anthropic route and set reasoning to high):

{
  "selected_byok_nickname": "openrouter",
  "byok_overrides": {
    "openrouter": {
      "provider": { "order": ["anthropic"], "allow_fallbacks": false },
      "reasoning": { "effort": "high" }
    }
  }
}

A JSON Schema ships with the CLI, so once you add $schema to your config, editors like VS Code will autocomplete and validate the fields. See the “Advanced: edit config.json directly” section of Bring your own API key for details.

These overrides apply only to the BYOK route — Blaze’s first-party route (via the LLM proxy) is unaffected.

5. Other improvements

• Fixed a bug where the /model picker would not scroll to follow the cursor when it moved past the visible area

• BYOK decryption is no longer done at startup when not needed, making non-BYOK startups noticeably faster

• Local state directories from external tools (sfhistory etc.) are now auto-ignored from Blaze’s git operations to prevent accidental commits

• New help articles for Bring your own API key and Using local LLMs — the wizard flow is now easier to follow