0.1.16

Download

Find your operating system — that row has the only file you need.

Your machine	Download
Windows 10 / 11 · 64-bit	Vibisual-0.1.16-setup.exe · 181 MB
macOS	Apple Silicon (M1 and later) — Vibisual-0.1.16-arm64.dmg · 194 MB Intel — Vibisual-0.1.16.dmg · 198 MB
Linux	Debian, Ubuntu, Mint — vibisual_0.1.16_amd64.deb · 134 MB Fedora, RHEL, openSUSE — vibisual-0.1.16.x86_64.rpm · 139 MB Arch, NixOS, anything else — Vibisual-0.1.16.AppImage · 162 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 | iex

The 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.app into /Applications, then run this once:

  xattr -cr /Applications/Vibisual.app

• Linux (.deb / .rpm) — your package manager pulls in the libraries for you:

  sudo apt install ./vibisual_0.1.16_amd64.deb
  sudo dnf install ./vibisual-0.1.16.x86_64.rpm

• 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.16.AppImage
  ./Vibisual-0.1.16.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.16

Fixed

• The macOS builds are back. Version 0.1.15 shipped with no macOS files at all — not a broken download, simply nothing to download, and because the release page builds its table from the files that actually exist, the macOS row disappeared rather than pointing at something that was not there. The cause was the code-signing slot: when the signing certificate is not configured, the build system supplies an empty value rather than no value, and the packager treats an empty path as a real one and stops on it. Both macOS builds spent all three of their retries on that and produced nothing, while Windows and Linux published normally — so the release looked like it had succeeded. Signing values are now kept under names the packager does not read, and are handed over only once a certificate is actually present.

Changed

• A release is titled with its version and nothing else. The list of releases is where you compare one version against the next, and a product name repeated down every row is not information — it pushes the number your eye is looking for to the right. Every release up to 0.1.14 was titled with the bare number; 0.1.15 arrived as "Vibisual 0.1.15" and broke the column. Titles are back to the number, past releases we titled ourselves are corrected as they are regenerated, and a title someone wrote by hand is still left alone.

Full history: CHANGELOG.md