Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: utmstack/utmstack-cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.0.0
Choose a base ref
...
head repository: utmstack/utmstack-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.0.1
Choose a head ref
  • 3 commits
  • 4 files changed
  • 2 contributors

Commits on Jul 20, 2026

  1. Clarify the two credentials, and that the SIEM connection is configur… 

    …able in-chat

The First-run section conflated two different systems on adjacent lines. It now
has a table that separates them: the ThreatWinds API key authenticates the LLM
(set via /connect), and the UTMStack connection reaches your SIEM (URL + API key
or username/password).

Documents that the UTMStack connection can be set either with utmstack-mcp init
or by simply asking the assistant, which now has configure_server/remove_server
tools — so both credentials are reachable from the CLI. Notes that the in-chat
path deliberately cannot enable remote command execution.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Rick Valdes @claude
    Rick Valdes and claude committed Jul 20, 2026
    Configuration menu
    Copy the full SHA
    b454843 View commit details
    Browse the repository at this point in the history

  2. Build on bun 1.3.13 to fix the Windows TUI (OpenTUI FFI crash) 

    `utmstack` crashed at startup on Windows with:
  Failed to initialize OpenTUI render library: bun:ffi dlopen() is not
  available in this build (TinyCC is disabled)

Root cause is Bun issue #30717: a regression that landed in bun 1.3.14 (the
Rust rewrite) drops the extraction step for FFI native libraries embedded via
`with: {type:"file"}` in `bun build --compile` output. OpenTUI — opencode's
renderer — loads its native library exactly that way, so the compiled binary
cannot dlopen it. On macOS/Linux a fallback masks it; on Windows, where TinyCC
is also disabled in compiled binaries, both paths fail and the TUI won't start.
1.3.14 is the latest Bun release and the fix (PR #30720) is in no release, so
the only path is to build on 1.3.13, the last release before the regression.

Verified on a real Windows 11 ARM64 machine: the 1.3.14 build exits immediately
with the FFI error; the 1.3.13 build gets past renderer init and runs. macOS
arm64 rebuilt on 1.3.13 and TUI-smoke-tested — no regression.

Pins packageManager and CI setup-bun to 1.3.13. Adds a BUILD_TARGETS env filter
to build.ts so a single platform can be built for testing without the full
matrix.

I had not tested the interactive TUI on Windows before the first release — only
the MCP end-to-end and the CLI's headless `run` path on macOS. That gap is what
let this ship. The release workflow's verify step still only checks --version;
a TUI smoke test in CI is a follow-up worth doing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Rick Valdes @claude
    Rick Valdes and claude committed Jul 20, 2026
    Configuration menu
    Copy the full SHA
    d40c01e View commit details
    Browse the repository at this point in the history

  3. Type the BUILD_TARGETS filter params (fix typecheck / pre-push hook) 

    targetKey's parameter was implicitly any, which failed `bun typecheck` and
blocked the pre-push hook, so the 1.3.13 Windows fix never reached the remote.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Rick Valdes @claude
    Rick Valdes and claude committed Jul 20, 2026
    Configuration menu
    Copy the full SHA
    0ba0ed1 View commit details
    Browse the repository at this point in the history
Loading