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: 0ba0ed1
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: 7bd9b6d
Choose a head ref
  • 3 commits
  • 3 files changed
  • 2 contributors

Commits on Jul 20, 2026

  1. Use tar for extraction in the Windows installer 

    Expand-Archive is very slow on Windows ARM for the ~62 MB many-file CLI zip —
slow enough that a fresh install can appear to hang for minutes and get killed
mid-extract, leaving no binary. tar (bsdtar, shipped on Windows 10+) extracts
the same archive in seconds; Expand-Archive remains the fallback.

install.ps1 is fetched from main, so this takes effect immediately for the
one-liner without a re-release.

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
    1b94f1c View commit details
    Browse the repository at this point in the history

  2. Windows: use the x64 build everywhere; drop the broken native ARM64 b… 

    …inary

The native windows-arm64 CLI cannot start its terminal UI. Verified on a real
Windows 11 ARM64 machine that opencode's OWN windows-arm64 binary crashes at
renderer init identically to ours (exit 1, FFI) — while both x64 binaries run
fine under Windows ARM64 emulation. So this is a Bun/OpenTUI toolchain
limitation, not our build, and shipping a native arm64 binary just hands users
a guaranteed crash.

Changes:
  - install.ps1 installs windows-x64 on both AMD64 and ARM64. On ARM64 it runs
    under Windows emulation, where the TUI works (verified).
  - Release matrix drops windows-arm64; ships windows-x64 only.

This matches opencode's effective support (their arm64 package exists but does
not run) and unblocks the user's ARM64 machine via the x64 emulation path,
which works against the existing v1.0.1 windows-x64 asset immediately.

Reverts the earlier "WSL required" guidance — WSL is not needed; x64 under
emulation is the native path.

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
    80341d7 View commit details
    Browse the repository at this point in the history

  3. README: document the real Windows story (x64 native, ARM64 via emulat… 

    …ion)

Reverts the WSL-required framing. Windows uses the x64 build — native on x64,
under emulation on ARM64, where the TUI works. No native ARM64 build ships
because it cannot start the renderer (same limitation as opencode's own).

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
    7bd9b6d View commit details
    Browse the repository at this point in the history
Loading