Skip to content
Blog

What's new in 0.12.0

A new look for the app, and plans from Lead that carry through. Neutral greys, a tinted tile for each engine and quieter pane headers. Follow each task's run and review, land the approved work in the plan's order, and find the plan again after a restart.

Naman Jain4 min read

Vibezeo 0.12.0 is out for Linux, as a .deb for Debian and Ubuntu and an .rpm for Fedora. Vibezeo is free and needs no account, and like 0.11.0 it runs on your computer, with nothing sent to our servers.

0.11.0 was about running several agents at once and staying in charge of them. This release gives the app a quieter look while they work, and lets a plan from Lead carry through from its first run to the landing.

A new look

With several agents working side by side, the app should stay out of the way, and you should see at a glance which agent is which and which ones are working.

  • A quieter look. Neutral ink greys in both the light and dark themes, and softer shadows in the light theme. A working agent shows a filled dot with a slow, breathing halo, which holds still when you reduce motion.
  • Engines are easy to tell apart. Each built-in engine has its own tinted letter tile in pane headers, the rail, the launch grid and threads.
  • Pane headers say where you are. A terminal pane's title names its folder, and an agent pane's names its engine and folder until the agent or your first prompt names the work. Tabs show the task in a few words, and the header's buttons stay dimmed until you point at the header.
  • Launch faster. The launch grid takes the number keys 1 to 9, marks the default engine, and copies a missing engine's install command with one click.
  • More in the status bar, only when it matters. It now shows agents working and waiting, the checks on a worktree's pull request, usage and listening ports, each only while there's something to show.
  • Threads summarise their work. In a Codex thread, and in an ACP agent's thread when the agent sends its edits as diffs, a finished turn counts the files it changed, with lines added and removed. Test runs from Vitest, Jest, cargo test or pytest show passed and failed counts in every thread.

Follow a plan through

In 0.11.0, Plan with Lead split a goal into tasks and ran each one once in its own worktree. Once the runs started, you followed them task by task.

Now the plan lists each task with its latest run: not started, queued, running, ready to review with the review's verdict (Approved or Changes requested), stopped, failed or done. A line counts them, and each row opens its task.

  • Land N approved… opens Land worktrees with exactly the approved tasks' worktrees chosen, in the plan's order. You check the forecast and confirm the landing there.
  • A plan stays in the Tasks page's header until you remove it, and comes back after a restart. Its chip there shows whether its runs are going, wait on you, or are done.
  • If Vibezeo closed while Lead was planning, the plan says so and offers Plan again. If it closed while Execute all was starting the runs, or while Create tasks was writing, the plan keeps what was done, and the next try does only the rest.

Chat threads claim the files they edit

In 0.11.0, Claude Code in a terminal pane claimed a file just by editing it. Now, in a thread on this computer, a Claude Code or Codex agent's edits claim their files too, and so do an ACP agent's edits that name their files, so agents in other worktrees of the repository see the overlap. An edit you refused, or one that failed, claims nothing, and a task run is asked to claim its files before it edits them.

Also in this release

  • Freeze could fail with "Couldn't freeze this pane" on a pane running one short command after another, when a command ended just as Freeze stopped it. This could happen in terminal panes, and in agent panes that run without a systemd user scope, where Freeze stops the pane's processes with signals. Freeze now keeps the pane's shell stopped instead, so the next command waits until you choose Thaw.

Update or install

On Debian or Ubuntu, check the download against its checksum, then install it:

sha256sum Vibezeo_0.12.0_amd64.deb
sudo apt install ./Vibezeo_0.12.0_amd64.deb

On Fedora:

sha256sum Vibezeo-0.12.0-1.x86_64.rpm
sudo dnf install ./Vibezeo-0.12.0-1.x86_64.rpm

Compare each checksum with the one on the download page. The full notes are in the changelog.

On the same subjects