Skip to content

Husk v0.1.1 - OAuth popups + Shell identity

Choose a tag to compare

View all tags
@runhusk runhusk released this 28 May 00:08
v0.1.1
ad1e7d0

Patch release on top of v0.1.0. Fixes the most-reported issue from the first 24h (OAuth popups not closing themselves) plus a Windows Shell quirk around taskbar pinning.

Downloads

File Size SHA-256
Husk-Portable-0.1.1.zip 1.8 MB b11a243a4ff72539351afe5f4776f12a5548c3408072b23d22df96baa01bd1c8
husk.exe (raw, for inspection) 4.0 MB de66fab1c0a90885aaba8f36f69ceede8ddb0e0c6af44db3796cef9ea5929d01

Verify before running

Get-FileHash .\Husk-Portable-0.1.1.zip -Algorithm SHA256

Match the output against the hash above. If it differs — do not run.

What's fixed

OAuth popups now close themselves

Logging in via Sign in with Google / Microsoft / GitHub / Apple used to leave the popup tab orphaned with a "you can close this window now" message — because Husk spawns popups as tabs (not native windows), so WebView2 didn't fire its native WindowCloseRequested event when the auth callback page called window.close().

Fix: window.close() is now intercepted by the content-init script and routes to the existing tab-close IPC. The tab closes on auth completion as users expect. The native WindowCloseRequested hook is also installed as defence-in-depth.

Taskbar pin identity (AUMID per install location)

Two Husk binaries on the same machine — say the official installer and a portable copy — used to share the same Windows Shell identity (Husk.Profile.default). Result: pinning the portable could resolve to the installed binary, so clicking the pin launched the wrong one.

Fix: the AUMID now includes a stable hash of the executable's directory, so each install location has a distinct Shell identity. Pinning the portable in folder A no longer collides with the installed binary in folder B.

Known limitation: Windows aggressively caches existing pin records. If you previously pinned v0.1.0 and re-pin v0.1.1, you may need to unpin first, close all Husk processes, and re-pin from the running portable for the cache to update. Fresh users are unaffected.

Everything else

Unchanged from v0.1.0 — same Argon2id + ChaCha20-Poly1305 vault, same DoH proxy, same anti-fingerprint stack, same boss key, same crypto source at husk-crypto.

Upgrade path

Drop the new husk.exe into your existing portable folder, replacing the old one. Your HuskData/ directory stays untouched — profiles, bookmarks, vault, notebooks all carry over.

Or extract the fresh zip to a new folder, copy your old HuskData/ into it, and run from there.

Coming in v0.1.2

  • OAuth popups will open as proper new windows (with the size the page requests) instead of tabs, matching mainstream browser behaviour
  • Mac and Linux work begins after this patch ships
  • More test coverage on the WebView2 → wry boundary

If Husk is useful to you, support keeps it free, ad-free and account-free: husk.run/donate.

Assets 3
Loading