0.1.14
Download
Find your operating system — that row has the only file you need.
| Your machine | Download |
|---|---|
| Windows 10 / 11 · 64-bit | Vibisual-0.1.14-setup.exe · 151 MB |
| macOS | Apple Silicon (M1 and later) — Vibisual-0.1.14-arm64.dmg · 164 MBIntel — Vibisual-0.1.14.dmg · 169 MB |
| Linux | Arch, NixOS, anything else — Vibisual-0.1.14.AppImage · 152 MB |
Not sure which Mac you have? Apple menu → About This Mac — "Apple M1/M2/M3/M4" is Apple Silicon, "Intel" is Intel.
The other 10 files under Assets — you do not need them
They are what the app's built-in updater reads: latest*.yml is the version feed, *.blockmap lets an update download only the changed parts, and *-mac.zip is the format macOS updates in place with. Downloading them by hand does nothing.
Or install with one line
# macOS and Linux
curl -fsSL https://raw.githubusercontent.com/Vibisual/vibisual/main/scripts/install.sh | sh# Windows
irm https://raw.githubusercontent.com/Vibisual/vibisual/main/scripts/install.ps1 | iexThe script reads this release, picks the build for your machine, and prefers your package manager over the AppImage when you have one.
First launch
-
Windows — the build is not code-signed yet, so SmartScreen warns on first run: More info → Run anyway.
-
macOS — unsigned too, and Gatekeeper blocks it outright. Move
Vibisual.appinto/Applications, then run this once:xattr -cr /Applications/Vibisual.app
-
Linux (AppImage) — for distributions that take neither format. It needs FUSE 2, which recent releases no longer ship:
sudo apt install libfuse2t64 # "libfuse2" on Ubuntu 22.04 and older chmod +x Vibisual-0.1.14.AppImage ./Vibisual-0.1.14.AppImage
Vibisual runs on top of the Claude CLI, which must already be on your PATH.
Day-to-day development and testing happen on Windows, so macOS and Linux get far less hands-on use. If a build is broken there, open an issue — we will fix it quickly.
What changed in 0.1.14
Fixed
- Pressing "Update" now actually installs the update. The installer was launched before the app finished shutting down, and it replaces the installed files by renaming them one at a time — which fails outright while
Vibisual.exeis still running. After five one-second retries it gave up with "Failed to uninstall old application files" and installed nothing, so from your side the app just closed and came back on the old version. The installer is now launched at the very last moment, once cleanup is done and the process is about to disappear. - Closing the app takes a moment instead of a minute. Shutdown waited for every open network connection to finish on its own — a phone still connected over LAN access, or an idle keep-alive socket, could hold it for over a minute (68 seconds, measured). Sockets are now cut when we have decided to close, and cleanup has a hard four-second ceiling after which the app exits regardless. Everything written to disk is flushed before that point.
- No second "work is still running" prompt when you update. The update button already warns you and asks for confirmation; the ordinary close-confirmation was then asking again about the same thing — and the time spent answering it was enough for the installer to give up.
Full history: CHANGELOG.md