v0.1.3 — release notes
2026-09-19 · download ·
macOS (Apple Silicon) first; the Linux AppImage stays on 0.1.1 while the
CI release build remains blocked. Every fix below was diagnosed on the
real machine that hit it.
0.1.3 is the "Simply Works on Mac" pass — the three
defects the owner hit testing 0.1.2: the SteamCMD download that did
nothing, a native Mac game (Cyberpunk 2077) routed at Proton, and a
Play button that silently did nothing. All three are fixed at the root.
1. SteamCMD on macOS actually installs now
- v0.1.2 pointed the macOS fetch at
steamcmd_macos.zip —
a URL that does not exist (HTTP 404). The real bootstrapper is
steamcmd_osx.tar.gz, the same source Homebrew's
steamcmd cask uses.
- Its payload is a universal binary — it runs
natively on Apple Silicon. No Rosetta needed for SteamCMD itself
(Rosetta remains a requirement of the Windows-Steam-client route).
- The download now shows a progress dialog from
whichever button started it, and every failure ends in an error
dialog naming what happened — the silent dead button is gone.
- An existing Homebrew steamcmd (
/opt/homebrew/bin/steamcmd)
is detected and used instead of downloading a second copy.
2. Native Mac games run natively — no Proton, no tools
- Steam sells native Mac builds of many titles (Cyberpunk 2077 among
them). v0.1.2 could not see them: the engine searched for Windows
.exe and Linux ELF only, so a Mac install planned as
"unresolved" while the database's Proton recommendation showed
through.
- The engine now detects
.app bundles and Mach-O binaries
by content (magic bytes, never extensions) and
plans them native — "runs directly, no
compatibility tools needed."
- The native build wins over any Proton/Wine
recommendation, with a warning that says so — and
Proton/umu are Linux routes, now gated off macOS everywhere,
including a user's own forced-Proton override (refused with the
reason, never a launch that cannot exist).
- Cyberpunk 2077's Mac build launches from the Play button with
zero tools — no Wine runtime, no prefix, nothing
downloaded.
3. Play is never silent — and mac-steam works from the window
- The window had no mac-steam launch path at all: a
mac-steam plan produced a failed attempt ("no command
for strategy") that the Library view rendered as nothing.
- mac-steam launches now run the CLI's own proven flow
— the code verified on this hardware (client install, one-time
login,
-applaunch, the recovery ladder) — as a
subprocess whose output streams into the launch log.
- Every refused launch names itself in a dialog with
the pointer to the full report, and an unplayable tile says why when
Play is pressed. The silent no-op is gone.
Honest status
- Verified on the M5 Pro Mac: SteamCMD's real URL and
universal binary (live fetch), Cyberpunk 2077 planning
native against the real install, the full offline gate
(≈3,400 checks; 53-check Steam suite).
- Not yet exercised live by the developer: a real
SteamCMD login with the owner's credentials, and a real mac-steam
launch from the window (the underlying flow was verified from the
CLI on 2026-09-18). If something hangs, the log panel shows the
CLI's own output — that is the bug report to send.
- The Linux 0.1.3 AppImage is not attached — the CI
release build remains blocked (GitHub Actions billing on the owner
account). Linux stays on 0.1.1; the download page says so.
- The bundle remains unsigned: Gatekeeper asks you to
confirm the first open; the download page's checksum is how you
verify it.
Upgrading
Replace the old app; registrations, prefixes, settings and history
live in the user state directories and are picked up on first launch.