v0.1.2 — release notes

2026-09-19 · download · macOS (Apple Silicon) first; the Linux 0.1.2 AppImage is pending (see the honest status below). Everything marked "verified" ran on real hardware; everything marked otherwise says so.

What 0.1.2 adds

Steam detection, fixed on macOS

• Detection now reads every Steam library this machine has: the per-OS install root (~/Library/Application Support/Steam on macOS), every folder libraryfolders.vdf names (including secondary drives), and Verjuice's own SteamCMD library. 0.1.1 read a Linux-only path — a fresh macOS install saw zero games.
• The Sources panel, the Steam tab and the launch path all read the same way, so they can never disagree about what is installed.
• Import from Steam: a checklist of everything already installed; you pick what to add. Nothing is imported silently, and titles whose executable cannot be confidently resolved are flagged rather than guessed.

Login to Steam & Install Steam Game (Library toolbar)

• Login to Steam runs the whole sign-in in one click: SteamCMD — Valve's own command-line client, about 2 MB, fetched with your consent — then your username and password (written to SteamCMD's own login, stored nowhere), then a Steam Guard code only when SteamCMD asks for one. The session is SteamCMD's own; Verjuice records only the username.
• Install Steam Game: type the game's name. It resolves against the compatibility database and Steam's public store search (a picker appears when several match), shows the compatibility verdict before any bytes download — an unsupported-per-database verdict is your choice to proceed, not a surprise after 80 GB — then downloads with a progress bar and a cancel that resumes rather than restarts.
• On Linux/macOS the Windows build is fetched (SteamCMD's own platform override) so a Wine/Proton backend has something to run; titles without a Windows build get their native one instead. Installs land in Verjuice's own Steam library, where detection and the launch pipeline find them.
• Distinct failures stay distinct: not-owned is not "network broke"; a cancelled download resumes; an expired session re-prompts the sign-in instead of hanging.

Account & CLI

• Connect Steam account (Settings → Steam): Steam's own OpenID page identifies you — no password or 2FA code ever passes through Verjuice — and the response is verified against Steam's check_authentication endpoint before your SteamID64 is stored. The owned-games list needs Verjuice's library backend, which is not shipped yet; the panel says so honestly rather than pretending.
• CLI: verjuice steam detect|import|connect|login|install|status|disconnect.

Also in 0.1.2

• Compat-database corrections: the frame-latency knob several entries recommended (DXVK_MAX_FRAME_LATENCY) does not exist in any DXVK release (full history searched 2026-09-17); entries now pass the real knob via DXVK_CONFIG="dxgi.maxFrameLatency = 1". Duplicate Steam appid links that broke database validation are collapsed.

Honest status (read before filing bugs)

• Verified on this machine: detection across real libraries, the bundled CLI surfaces, and 48 new offline checks; the whole offline gate (≈3,400 checks) passes except four pre-existing host issues unrelated to Steam.
• Not yet exercised live, by design: a real SteamCMD login with your account and a real multi-gigabyte download were not run by the developer — they need your credentials. The login parser is tested against scripted SteamCMD output for both Steam Guard wordings (email and mobile). If a sign-in hangs, the advanced panel shows SteamCMD's raw output — that is the bug report to send.
• The UI dialogs (login, store picker, install progress) follow the shipped dialog patterns and pass the offline suites; the first real click-through is yours.
• The Linux 0.1.2 AppImage is not published yet — the release build is temporarily blocked (GitHub Actions billing on the owner account). v0.1.1's AppImage remains the current Linux build; the macOS build carries everything in these notes.
• The bundle remains unsigned: Gatekeeper asks you to confirm the first open, and the download page's checksum is how you verify it.

Upgrading

Replace the old app with this one. Your registrations, prefixes, settings and history live in your user state directories — deleting the old app never touched them, and this one picks them up on first launch.