Skip to content

0.1.7

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Jul 07:43
· 36 commits to main since this release
v0.1.7
465108a

Download

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

Your machine Download
Windows 10 / 11 · 64-bit Vibisual-0.1.7-setup.exe · 97 MB
Linux Arch, NixOS, anything else — Vibisual-0.1.7.AppImage · 122 MB
The other 3 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.

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

Added

  • Side-by-side diffs in the agent stream. When an agent edits a file, the change now renders as a before/after diff — red for the old lines, green for the new — with the changed words within a line highlighted, right in the output. Brand-new files show as a Created card, and multi-edit changes stack each hunk in order.
  • Turn your feedback into an agent's rules, from its panel. The agent section of the detail panel now tallies the like / dislike feedback you've left for that agent, and when there are dislikes it offers Promote to rules: a distilled set of proposed rule sentences you review and edit in a confirmation dialog before they're appended to that agent's Agent Rules. Nothing is applied automatically, and you can undo via Rules history. Per-session feedback counts are shown alongside the stream.
  • Performance profiler in the Debug panel. Profile now collects a one-minute frame profile, and one is also captured automatically when the frame rate drops below the threshold (with a cooldown), attributing which scripts held frames the longest. The result is a copyable report you can share to diagnose a slowdown.
  • Reload without restarting. New Reload session and Reload project actions refresh the current IDE session and the canvas project in place.
  • Fullscreen canvas and zoom reset. The canvas controls gain a fullscreen toggle and a one-click zoom Reset.
  • Phone back button acts as Escape. When you're viewing Vibisual from a phone, the browser's back gesture now closes the current overlay instead of leaving the app.

Fixed

  • Projects and tasks survive a crash. The project index (app-state.json) and each project's metadata (project.json) are now written atomically with rotating backups, and project metadata self-heals from the checkpoint or identity file (and their backups) when it's missing or truncated — the same protection the stream files already had. A crash mid-write no longer empties the canvas or drops projects on the next launch.
  • Crash causes are now saved to disk. Fatal errors — uncaught exceptions, unhandled rejections, and renderer / GPU process deaths — are appended to a rotating crash log, and native crashes are captured as local minidumps under the app's data folder, so a crash in an installed build can be diagnosed after the fact instead of vanishing with the process. Nothing is uploaded.
  • No more orphaned processes on Windows. When an agent stops, its whole process tree — including the node workers and MCP servers the CLI spawns — is now terminated together, instead of leaving grandchild "Claude Code" processes piling up in Task Manager across a long session.

Full history: CHANGELOG.md

Assets 7
Loading