Changelog - Vibrai

August 29, 2026

Opt-in crash reporting and a bug-report command, three new ways to work with a Live set (switch playback modes, clear clips while keeping your rig, capture large sets in pieces), and a run of vibrai update reliability fixes.

Opt-in telemetry and `vibrai feedback`

vibrai telemetry enable / disable / status control whether anonymized crash reports and coarse operation traces are sent to help improve Vibrai’s reliability. Default is off, and even switching it on sends zero bytes unless a delivery destination is separately configured — only the CLI can grant or revoke consent, never an agent on your behalf. See the telemetry privacy policy for exactly what is (and is never) collected. vibrai feedback "<message>" sends a scrubbed diagnostic bundle when you’re consenting, or saves it to a local file otherwise, so a bug report always has something to attach.

Switch between Session and Arrangement playback

vibrai transport playback-mode session|arrangement fires a scene or returns your tracks to the Arrangement, from the CLI or MCP — no more reaching for the mouse mid-session.

Clear a set’s clips, keep the rig

vibrai clip clear-all empties every session and arrangement clip while leaving tracks, instruments, effects, mixer settings, and scenes untouched — reuse a set you’ve already built for a fresh generation run instead of starting from a blank project.

Capture large sets in pieces

Capturing and generating now show live progress instead of sitting quietly. vibrai capture --track-ids captures only the tracks you name; vibrai capture-merge recombines two or more partial captures into one project, so a big set no longer has to fit inside a single request.

`vibrai update` reliability

An RC build now correctly recognizes the final release that follows it as newer, instead of reporting “up to date” forever. vibrai version no longer falsely warns about a stale bridge after a normal update. vibrai update refreshes its own bundled copy of the M4L device and Python bridge, not just what Live loads. And running vibrai update with sudo no longer leaves your Ableton Library files owned by root, which used to break the next reinstall.

Also

vibrai generate --json and vibrai capture --json no longer mix progress-bar text into the JSON output — a script parsing the result now gets clean JSON every time.

August 22, 2026

A fix release ahead of launch: undo brackets stop over-reporting, rapid back-to-back calls no longer trip the bridge, new projects are reproducible, and genre lookups by name go from seconds to milliseconds.

Undo brackets tell the truth

A bracket’s undo_bracket field reports "native" only when the close really closed this bracket — a lost inner close no longer lets the outer one claim success. Session export (vibrai session export / export_session) also stops replaying a stale undo token from a CLI-recorded vibrai undo begin / vibrai undo end, and renders set_track_auto_numbering as a valid vibrai track auto-number on|off line.

Rapid calls no longer trip the Python bridge

The bridge inside Live now keeps a connection alive between requests (HTTP/1.1), so a second or third quick call on the same connection no longer fails with a reset or a spurious 400. This was the root cause of 1.6.4’s “unreliable close after a Max-for-Live write” limitation. After you reload the Vibrai control surface in Live’s preferences, a stale connection gets a clear 503 instead of an answer from the old instance.

A device delete can no longer remove the wrong device

If Live’s reply to a delete_device / vibrai device delete was lost and Vibrai retried, the retry used to check the device’s position — which shifts after a non-last delete — so the wrong device could go. It now reads the chain before deleting and treats any shrink as proof the delete landed.

New projects are reproducible

apply_genre / vibrai genre apply and init_project / vibrai project init mint the same t2m_hash for the same project name every time. Note: a name now produces a different — but stable — hash than earlier runs did; projects you already have keep theirs.

Genre lookups by name: ~6 s → milliseconds

apply_genre "Deep House", start_genre_song, and even an unknown-genre error message used to re-parse the whole genre catalog. They read a summary index now. (vibrai genre list / list_genres still take the long path — tracked separately.)

Compressor writes say when they settled for the nearest position

apply_compression_preset / vibrai mix compress now mark each parameter exact: true|false, warn when a target had no exact position on the device (the Glue Compressor’s stepped Attack/Release ladders), and show ~ nearest to <target> in the CLI table.

Also

vibrai version’s “another vibrai earlier on PATH” warning no longer claims a Homebrew install that isn’t there or tells a dev build to uninstall; its advice now matches what the two copies actually are.
The macOS installer can no longer leave ~/Library/Application Support/Vibrai owned by root, even if the install step fails partway.
vibrai update rejects a malformed downloads-index version before using it in a URL.

August 21, 2026

One Cmd-Z for a whole sequence of changes, a new home for downloads, and a version warning that finally points the right direction.

Group changes into a single undo step

vibrai undo begin / vibrai undo end (MCP: begin_undo_step / end_undo_step) open and close a native Live undo bracket around any number of changes, across any surface — one Cmd-Z reverts all of it. generate, apply_automation_template, and render_automation (also reached via vibrai automation render and generate --with_automation) now bracket themselves automatically; their results carry a new undo_bracket field reporting whether the grouping actually took.

vibrai undo begin --label "big edit"
# ...any number of changes, on any surface...
vibrai undo end --token <token>

Known limitation: under fast, back-to-back automated calls, closing a bracket right after a Max-for-Live write can unreliably fail — the field correctly reports "unavailable" when this happens, and the change itself still goes through either way. The root cause is still open.Breaking: vibrai undo begin / vibrai undo end now return exit code 4 on a bridge/Live-side failure, matching every other bridge-touching command, instead of the generic 1 they returned before.

Downloads moved to downloads.vibrai.com

Installs and vibrai update now come from Cloudflare, not GitHub Releases. If you’re on 1.6.2 or earlier, the old updater checks a feed that no longer receives new releases and will report “up to date” forever — grab one fresh copy from vibrai.com/download and every update after that works normally again.

The version warning now says which side is behind

vibrai version and get_version used to warn “an older Vibrai than the CLI” for any mismatch — including when the bridge running inside Live was actually the newer one, which restarting Live can’t fix. It now tells you correctly: restart Live for an older bridge, update the CLI for a newer one.

Also

The Windows installer icon now matches the current mark at every size.

August 19, 2026

A fix release with audible consequences: five drum parts stop copying the kick, break placement respects your meter, and the installer no longer refuses while Live is open.

Five drum parts stop copying the kick

HiHatPlus, Percussion, Crash, Fill and Roll had no Euclidean cell of their own and all fell back to the same generic 4-pulse pattern — a crash hit, a drum fill and a shaker produced the identical rhythm, differing only by seed and pad. Each now has its own cell, authored per part and verified by ear.This changes generated output. Presets using those five part types generate different notes than in 1.6.2. Other part types are unaffected.

Break and fill steps follow the declared meter

BreakOverlay derived step offsets from a hardcoded 4/4 sixteenth while already carrying the real meter, so at any non-4/4 meter step N landed on the wrong beat. It now uses meter.BeatsPerBar / 16.0, the same grid the rest of generation uses — which also realigns break notes with the shadow kick grid.

The installer no longer refuses while Live is running

It warns and proceeds instead of failing, and tells you to restart Live. Live loads the Vibrai device and remote script at startup, so an install over an open Live has no effect until you restart it.Nothing inside a macOS .pkg can print to your terminal, so vibrai version reports it instead — it names any bridge serving a different build than the CLI, comparing build SHAs when the version strings match.

vibrai version

Breaking: three `--json` fields reported the wrong value

notes set / notes add ↔ write_notes / add_notes / modify_notes reported a raw 0-based scene_index beside an already-converted 1-based track_id. The write was always correct; only the report was off by one. Remove any compensation you added.
automation render ↔ render_automation now agree on track_id.
generate emits warnings: [] rather than null when empty, matching plan.

Also

12 shipped genre files carried automation: blocks targeting nothing, silently skipped every render. Removed.
vibrai update reinstalls the Ableton side before swapping binaries, so a mid-update failure can no longer leave new binaries beside an untouched device.
The MCP user guide now documents all eight generate-time style knobs.

August 16, 2026

A knowledge layer for mixing, bar lines that land on your set’s real meter, and a generate that asks before it duplicates your tracks.

Mixing advice, with the reasoning attached

Vibrai could already set a level, a pan and a send — but not tell you what to set them to. Mix profiles answer that per part type: a starting level, a pan position, a depth tier on the front↔back axis, and the corrective EQ and compressor moves that belong on that part, each with its reason.

vibrai mix profiles
vibrai mix suggest --chains
vibrai mix apply-profile --reverb-return "Reverb"

mix apply-profile writes the placement half only. The EQ and compressor numbers stay advice on purpose: a Live parameter’s real range is only knowable from an open set, so a profile cannot honestly pre-compute what to send.A part whose depth calls for a send, on a set where you named no return track, is applied for level and pan and then warns. Vibrai will not invent a return track for you.

Look up what to reach for

Knowing a mix is muddy is easy; knowing whether that wants EQ, compression, a dynamic EQ or automation is the hard part.

vibrai mix advice                  # the index
vibrai mix advice --subject kick   # compression starting points for a kick
vibrai mix compress 1 "Compressor" --for kick

mix compress does not yet reach Live’s own Compressor or Glue Compressor. The starting points are in milliseconds; both devices report those parameters as normalized 0–1, and Vibrai refuses a value it cannot send honestly rather than guessing. On those two devices it writes nothing and tells you why. That refusal is the feature working — threshold is never written at all, because it depends on the incoming level, which no table can know.

Bar lines land on your meter

On a 7/8 project, automation write, arrangement place and seek used to read 2.1 as beat 4.0 while generation put bar 2 at 3.5. All of them now resolve your project’s declared time signature first, then Live’s transport. The song wizards plan at that meter too, instead of planning at 4/4 and rendering at yours.

`generate` asks before duplicating your tracks

On a set that already has MIDI tracks, vibrai generate used to quietly append a second set alongside them. It now stops and asks:

vibrai generate --on-existing-tracks replace   # delete them, render fresh
vibrai generate --on-existing-tracks append    # add alongside

The MCP tool has always refused this way. If you have a script relying on the old silent append, add the flag.

Also

An unseeded Wander curve now sounds the same on every run. Reading notes back from an arrangement clip retries like its session-view twin. brew install warns when an older standalone install shadows it on PATH.

August 8, 2026

Ask for a key and actually get it, an install that no longer dead-ends in a hidden folder, and automation that runs once your instruments are loaded.

Ask for a key and get it

A genre preset used to decide the key for you. Now you can say what you want:

vibrai genre apply techno hypnotic_1 --scale-root D --scale-name Dorian

The same --scale-root / --scale-name pair works on vibrai start genre-song, vibrai plan and vibrai generate, and on their MCP twins apply_genre, start_genre_song, plan and generate. Vibrai re-keys the composition as it renders, in one pass — not by writing the preset’s key and transposing afterwards.Leave it out and nothing changes: the preset’s own key wins. Vibrai only reads the key from your open Live set when nobody has chosen one, and parts or sections pinned to their own scale are never re-keyed.Chords follow the mode now too. Vibrai’s two chord banks were fixed to Aeolian and Ionian whatever you asked for, so a Dorian project got Aeolian harmony. Roots and thirds are now built from your project’s own mode. Every shipped genre defaults to Minor, so their output is unchanged — this shows up when you ask for something else.

The Claude Desktop bundle, somewhere you can find it

If you installed from the macOS .pkg, dragging Vibrai.mcpb into Claude Desktop is the only way to connect the two — and that file lived in /usr/local/lib/vibrai, which Finder hides.

vibrai install claude-extension --reveal

That puts the bundle in your Ableton User Library under Vibrai/ and opens a Finder window with it selected, ready to drag into Claude Desktop → Settings → Extensions. Vibrai finds your real User Library from Live’s own preferences rather than guessing. vibrai install all does it as part of a full install; install_claude_extension is the MCP equivalent.

Automation is its own step

vibrai generate used to write automation during the render — before the instruments were loaded, so anything aimed at a track it had just created had nothing to aim at. It failed every time, and an explicit automation slot stopped the render outright.Automation now runs after the instruments do:

vibrai generate --project my-song.vibrai
vibrai automation render --project my-song.vibrai

Or ask generate to do it inline, as the last thing it does:

vibrai generate --project my-song.vibrai --with-automation

Targets it can’t resolve are no longer fatal — each is reported with the device it looked for and the controls that device actually has. render_automation is the MCP equivalent.One thing to watch: if a bounce fails and can’t restore your arrangement clips, the CLI exits with code 13 and the MCP response carries a data_loss message. That means clips were deleted and did not come back — check that field rather than counting skips.

Turn track numbering on and off

Ableton shows a leading # in a track name as the track’s position, so # Bass displays as 1 Bass. Vibrai could write that token but never remove it, so a numbered set had to be renamed by hand.

vibrai track auto-number off

It sweeps every track in the open set, and only strips a number that matches the track’s own position — a track called 808 Bass is left alone. Add --persist to make it the project’s default. set_track_auto_numbering on MCP.

Where a project file lands by default

This changes what an existing command does. Leave out --project and Vibrai used to reach for Untitled.vibrai. It now uses the name of the directory you’re in — so working in ~/Music/dawn-chorus gives you dawn-chorus.vibrai.If you have projects called Untitled.vibrai, commands that used to find them won’t any more. Rename the file, or pass the path explicitly. Where Vibrai can tell that’s what happened, it says so in the error.

Fixed

The install guide described a command that doesn’t exist. vibrai install status was never real, and the guide said the .pkg registers the MCP server with Claude Desktop for you — it doesn’t, and nothing in Vibrai writes that config file. Claude Code now gets its own instructions instead of reusing Claude Desktop’s.
generate --create-missing-tracks no longer duplicates a track that’s sitting right there. Reordering or rebuilding a set moved the track ids a project remembered, so the match missed and Vibrai created a second copy. It now finds a bound track by the name it saw, and writes the resolved ids back to the project file.
vibrai uninstall --user <name> now removes that user’s Claude Desktop entry and app data. Uninstall re-runs itself under sudo when it needs to, and those two steps were reading root’s home instead — reporting success while leaving your files untouched.
The first-song and genre-song wizards apply automation again, and tell you what landed. Splitting automation out of generate left them writing none of it, silently.
The session journal records the command that actually ran. Seven flags were being dropped from recorded MCP calls, producing a shorter command that still looked right.
vibrai shell appears in vibrai --help and in the published reference. It always worked; it was invisible to everything that documents it.

August 5, 2026

Vibrai used to assume every song was in 4/4. It doesn’t any more — and you can now shape a sound directly, instead of only automating it.

Songs that aren’t in 4/4

Tell Vibrai the meter when you start a project:

vibrai project init --time-signature 7/8

Leave it out and Vibrai follows whatever Live’s transport says, exactly as before. A real time signature now runs through the whole engine, so 3/4 and 6/8 stay different things rather than both becoming “three beats a bar” — bar lengths, clip lengths and arrangement placement all follow the meter you asked for.

Shape a sound, don’t just automate it

Automation moves a control over time. Sometimes you just want the filter set where you want it. Three new pairs do that:

vibrai device set-param 2 "Auto Filter" Frequency 0.5
vibrai device set-param 2 "Auto Filter" "Filter Type" Band-pass

Enum controls read back by their real names — Band-pass, not 4. vibrai automation params <track> <device> lists everything a device exposes, vibrai device apply-params sets several at once, and vibrai device set-state bypasses or re-enables a device. All three have MCP twins: set_device_param, apply_device_params, set_device_state.

Wizards that actually run

The first-song and setup flows now execute on both the MCP server and the CLI, instead of being instructions you follow by hand.

Also new

Generate can create missing tracks. If a project references a track that isn’t in your set any more, vibrai generate --create-missing-tracks makes it instead of failing. Without the flag you now get a clear error naming the missing tracks before anything is written, rather than a half-finished set.
Clips report whether they’re playing. vibrai clip get and clip list carry is_triggered (queued, counting in) and is_playing (actually sounding).
vibrai stock show accepts the name you can see in stock list, not just an exact path.

Fixed

Notes written past the end of a clip are now refused, naming the clip length and which notes are out of range. Before, they were silently mangled and reported as a success.
Audio effects load at the end of the device chain, where you’d put them — not in front of your instrument.
capture_project no longer fails on any set containing a Wavetable.
Claude Desktop no longer runs out of memory during long sessions.
Commands that can’t do anything useful with your input now say so instead of exiting quietly.
genre help examples are quoted properly, so pasting one works.
uninstall --help describes what it actually removes by default.

August 3, 2026

You can mix your set, colour it, and change a single note — three things Vibrai simply could not do before.

Before you upgrade

Project files move to a new version. Your .vibrai files gain the extra note information described below, and older files upgrade automatically the first time Vibrai opens them. The one thing to know: a project saved by this version and then opened by an older Vibrai loses that extra information. If you share project files with someone on an older version, upgrade together.

A real mixer

Vibrai could write notes but never touch your mix. Now it can set volume, pan, mute, solo, arm and sends on any track — and apply a whole mix in one go, keyed by part type. “Bass up two, pads back, more reverb on the lead” becomes a single instruction rather than a pass through Live’s mixer by hand.Ask what returns your set has and Vibrai will list them, so you know the names your sends can point at.

Colour

Tracks, scenes, session clips and arrangement clips can all take a colour from Live’s palette, and arrangement clips can be renamed. A generated set arrives looking like something you laid out on purpose instead of a wall of identical grey blocks.

Change one note, not the whole clip

Editing a clip used to mean rewriting every note in it. You can now change or delete specific notes and leave the rest alone. Vibrai checks the notes exist before it changes anything, so a mistake stops the edit rather than half-applying it.Notes also carry more of what Live actually knows about them — how likely a note is to play, how much its velocity varies, how hard it is released, and whether it is muted. Vibrai used to discard all of that on read.

Loops that vary as they play

Turn on native randomization and Vibrai hands the variation to Live instead of baking it into the notes, so a loop plays slightly differently each time round rather than repeating identically. It is off by default: you are trading exact repeatability for movement. Timing jitter stays baked in either way — Live has no per-note timing setting for Vibrai to hand over.

Fixes

Group tracks no longer confuse Vibrai — or cost you a track. Vibrai predated Live’s group tracks and treated a group as an ordinary MIDI track. Generating into a set containing groups could delete the last real track in it, or place new tracks one slot too far right. Capturing a set produced a phantom part for the group that matched nothing you could play. Groups are now recognised everywhere Vibrai reads your set.
Updating no longer fills your disk. Every update left roughly 182 MB of old binaries behind and never removed them, so upgrading a few times quietly cost a gigabyte. The backup is now disclosed and reclaimable.
A mistyped option is refused instead of ignored. Misspelling an optional setting used to be dropped silently, so a command looked like it worked while doing something other than what you asked.
Long note writes survive a slow moment. Writing more than fifty notes at once could leave a clip holding only some of them if Live stalled part-way through.
Genre files that cannot migrate cleanly now say so instead of migrating wrongly — for files built by merging extractions recorded in different keys.

August 1, 2026

Your tracks sound better — and they sound different. Melodic parts get real rhythm and memory, bass finally moves, and harvested phrases become reusable.

Before you upgrade

The same project and the same seed now render differently. Four improvements land on the melodic engine at once, so re-generating an existing project produces new parts rather than the ones you had. That is the point of the release — but if there is a render you want to keep exactly as it is, capture it before upgrading.Your genre files upgrade automatically the first time Vibrai opens them. Drum patterns you harvested with --faithful are now stored as actual pad numbers instead of relative to the key they were recorded in, so a captured beat lands on the right drums whatever key you play it in. One thing to know: if you built a genre file by merging two extractions recorded in different keys, only one of those keys can be recovered — if a harvested beat sounds wrong afterwards, extract it again.

Bass that moves

Bass used to sit on the root note. It now has six ways to move — root, root and fifth, octave pump, arpeggiated, walking, and pedal — picks notes that fit the chord underneath it, leads smoothly from one note to the next, and can walk into the next chord with an approach note. It also knows about the kick drum, and can lock to it, dodge it, or ignore it. All 14 genres ship with their own setting, and you can override it per render with --bass-motion and --kick-relation.

Melodic parts with rhythm and memory

Melodic parts (bass, riff, arp, lead, melody, solo, hook) used to scatter notes across every sixteenth. They now play real rhythms with real note lengths, repeat from bar to bar, and turn around at the end of a phrase. They also remember a motif and develop it instead of wandering. A new --gate control sets how long notes ring, from staccato to legato.

Harvested phrases you can reuse

A phrase you captured from your own playing used to replay only in the exact section you lifted it from. It can now be reused anywhere in the track, refitted to whatever chords that section is playing. Drum grooves get reused too, but never refitted — moving a groove to a different chord would land it on different drums rather than transposing it. New vibrai phrase list and vibrai phrase remove commands let you see what a genre file holds and prune what you do not want.

Everything in a section agrees on the chords

Parts within the same section could each roll their own chord progression and disagree with one another. They now share one progression.

Fixes

Hand-edited .vibrai files are checked now — a file that used to load may be rejected. Vibrai used to ignore fields it did not recognise when reading notes from a project file. A mistyped start: instead of start_time: quietly became a playable note in the wrong place, which looked like a generator bug rather than a typo. Those files now fail with the field name, a suggestion, and the line number. Every project file shipped with Vibrai still loads unchanged, but if you hand-edit .vibrai files, a mistake that used to pass silently will now stop you.
--clear-first really does clear. When every track in a set was made by Vibrai, one track survived with its clips intact — so an old composition kept playing underneath the new one. Live refuses to delete a set’s last track, so Vibrai now empties it instead, and tells you it did.
Renders survive a slow Live. A render could fail outright and leave a half-finished set when Live took too long to accept a batch of notes. Vibrai now checks whether the notes actually arrived and retries only when they did not.
Note data is checked instead of quietly ignored. Mistyped fields in a note used to be dropped silently, which could pile every note onto the first beat. Bad note data is now rejected with a real error.
Retargeting drums picks the right tracks. drums retarget could bind parts to the wrong tracks, and a run that matched nothing finished silently instead of saying so.
Genre files cannot be truncated. An interrupted save used to be able to destroy everything in the file — phrases, palettes, presets. Saves are now all-or-nothing.
project save writes a loadable file when the project does not exist yet.
Version reporting is accurate. vibrai version could show a stale “latest version”, and now always reports the status of each bridge so a hang is not mistaken for an outage.

Also new

vibrai skill serves Vibrai’s playbook and full command reference to AI clients that cannot read it any other way.

July 24, 2026

Clear-before-generate, automatic Max for Live bridge recovery, and a batch of CLI fixes.

Clear-before-generate

Generating a different project into a Live set that already held a previous one used to stack the new tracks on top of the old ones — up to three compositions could pile up audibly. New project clear command and a generate --clear-first flag remove the previous Vibrai-generated tracks first, so a fresh generate replaces instead of stacks. It never touches your own tracks — only tracks Vibrai created. Both surfaces (clear_project, and a clear_first option on generate).

Automatic Max for Live bridge recovery

When Max for Live gives up respawning Vibrai’s bridge after repeated crashes, Vibrai now recovers on its own instead of leaving you to reload the device by hand, and shows a clearer “bridge unavailable” message while it’s down.

Fixes

Snake_case part types are now accepted in the commands that previously rejected them — the real cause of the earlier hi_hat/fx_* “gaps.”
project init no longer overwrites an existing project. Pointing it at an existing project file used to silently replace it; it now refuses instead.
--json is honored on project init, genre apply, and project save, which previously fell back to plain text.
instruments untag now reports what it actually removed instead of always claiming success.
Long file paths in command output are no longer corrupted by line-wrapping.

July 19, 2026

Fixes an intermittent startup crash on Apple Silicon Macs.

Fixes

Intermittent startup crash on Apple Silicon fixed. On Apple Silicon Macs the CLI and MCP server could crash on launch roughly 10–15% of the time, regardless of the command, because of a .NET runtime defect in compressed application bundles. Those builds now ship uncompressed and start reliably. The on-disk binaries are larger as a result; compression will return once the underlying runtime fix ships. Intel Macs and Windows were unaffected.

July 19, 2026

Three fixes: corrected genre catalog data, more reliable device/clip deletion under heavy load, and device load now accepts the same path shown by stock list/stock browse.

Fixes

Genre catalog labels corrected. Every preset in the Rock & Country and Reggae & Dancehall genres had been mislabeled with the wrong sub-genre; they’re now tagged correctly. A stray placeholder preset was also removed from the Dance & Mainstage genre.
More reliable device and clip deletion under load. A rare race during heavy use could cause a retried delete to remove the wrong device from a track. Deletes now confirm the target is actually still there before retrying.
device load --path now accepts stock catalog paths directly. Copying a path straight from stock list/stock browse’s output used to fail with “device not found” — it now loads correctly, matching what stock load already did.

July 18, 2026

New ways to package the Vibrai Agent Skill for Claude Desktop, a few new guided MCP wizards, and two install-time fixes.

Claude Desktop Skill packaging

Claude Desktop’s Skills feature only accepts a manually-uploaded .zip, unlike the directory-based install Claude Code, Codex, and Gemini CLI use. Vibrai now supports it directly:

vibrai skill package produces a ready-to-upload .zip (add --to <path> for a custom location).
Running vibrai skill install or vibrai skill path with --target claude-desktop now points you at the new command instead of erroring.
The same packaging is available as an MCP tool, so an AI assistant connected to Vibrai can produce the zip on your behalf.

New guided wizards

Four new guided prompts for AI assistants connected over MCP — each walks the assistant through an existing capability step by step: wrapping up a session (capture + export), finding a stock sound, swapping a drum kit, and authoring automation.

Fixes

brew install/self-update installs now include the starter templates. A packaging gap meant vibrai install templates (and install all) failed right after the Homebrew or self-update path finished installing everything else — the standard .pkg installer was unaffected.
The Max for Live device’s status page loads correctly after install. A copy step was skipping a nested folder, so the in-Ableton status page showed a blank error instead of Vibrai’s status.
The extension’s install listing now links to the real support/documentation pages instead of the private development repo.

July 17, 2026

Play songs from Session view, and a round of macOS installer hardening found during 1.2.0’s own post-release checks.

Session-view scene playback

Play a song by firing Session scenes — playback can now be driven from the Session view, on both the CLI and MCP surfaces, not just the arrangement.

macOS installer + uninstall hardening

uninstall --purge-data run with elevated privileges no longer resurrects the profile directory as root, which had been leaving behind root-owned files a normal user couldn’t clean up.
A missing or unreadable license file no longer crashes Vibrai — the license check now fails open instead of aborting.
The postinstall step repairs profile-directory ownership before Ableton Live or vibrai ever runs as your normal user account.
The installer now runs natively on Apple Silicon during install/uninstall scripts, instead of under Rosetta translation.
Uninstall diagnostics are now captured and reported instead of silently discarded, making it easier to tell what happened if an uninstall doesn’t fully clean up.

`.mcpb` manifest fixes

The install prerequisite now correctly states Ableton Live 12+ (an arrangement-clip feature the manifest relies on is Live-12-only; the manifest previously said 11+).
The Claude Desktop extension listing’s license, homepage, and repository links now point at the correct commercial-license terms and public pages instead of an incorrect open-source claim and a private repo.

July 16, 2026

Automation you can trust, smaller installs, and a new way to install Vibrai — plus a more reliable connection for AI assistants.

Automation you can trust

A round of fixes to how automation curves are written and read back:

Curves land where you expect them. Automation values now scale correctly to each parameter’s real range, instead of sometimes landing squashed into the wrong part of the dial.
Generated songs are audible. A quiet bug meant some automation written during song generation didn’t actually move the sound the way it looked like it should — fixed, so what you hear now matches what you designed.
Clip names survive automation writes. Writing automation over a named clip no longer blanks out its name.
Bad automation values are caught immediately instead of being silently saved and only causing trouble later.
Automation pushed live now reads back correctly, instead of silently disappearing the moment you check it.

Auto-numbered tracks

An optional setting adds Ableton’s own # auto-numbering to tracks Vibrai creates, so your track names stay numbered in order as you rearrange your set — just like tracks you number by hand.

Smaller installs, more reliable updates

Installs are roughly half the size they were, with no change to download size and barely any extra startup time.
The Claude Desktop extension no longer bundles the standalone command line tool it doesn’t need — a leaner extension.
Uninstalling no longer ends in a crash.
Updating from Claude Desktop now refuses safely instead of overwriting the wrong file, when it can’t tell exactly what it’s updating.
A permission problem during an update now tells you how to fix it, instead of showing a raw error.
The bundled starter templates now actually show up in Ableton’s browser.

A new way to install: Homebrew

If you use Homebrew, you can now install Vibrai with:

brew install vibrai

right alongside the existing installer and self-update options.

A more reliable connection for AI assistants

Vibrai’s AI-assistant interface (MCP) now addresses tracks and scenes with stable, reliable references instead of plain numbers — closing the door on a subtle class of bug where an assistant could end up talking to the wrong track or scene. If you’ve built your own integration against Vibrai’s MCP tools, track and scene ids now come back as short reference strings rather than bare numbers; everything else about talking to Vibrai from the command line is unchanged.

Fixes and polish

Placing a clip over an already-occupied spot in the arrangement no longer times out.
Scene commands now support --json consistently from the command line.
Inserting a scene at a specific position now actually inserts it, instead of always adding it to the end.

July 13, 2026

Cleaner install and uninstall, drive Vibrai from your coding agent, and a smoother activation experience.

Install, update, and uninstall — cleanly

Getting set up (and unset) is simpler in 1.1.0:

Bundled Live Sets — the installer now ships two ready-to-open Ableton Live Sets, Vibrai Starter and Vibrai Demo, so you have a correctly-wired project to open the moment you’re installed.
One-step updates — vibrai update now updates the built-in server together with the command line in a single step.
One-command uninstall — vibrai uninstall removes Vibrai cleanly, showing you a plan of exactly what it will remove before it touches anything.

Drive Vibrai from your coding agent

Vibrai now ships an Agent Skill — a portable skill that installs straight into your coding agent (Claude Code and other skill-aware CLIs). Once it’s in, your agent knows how to drive Vibrai on its own: generating genre tracks, building arrangements, loading instruments, applying automation — going from a cold session to an audible result without you wiring anything up.

vibrai skill install

Your agent uses connected Vibrai tools when it has them, and the vibrai command line otherwise.

A smoother activation experience

If you reached your machine limit, activation used to point you to a page that can’t actually free a seat. It now points you to support@vibrai.com, who can.Activation also sends less about your machine — your computer’s name is no longer transmitted. The registration label is just your operating system plus a random tag (like macos-a1b2c3d4), and a new command shows you exactly what’s sent, and nothing more:

vibrai license privacy

Fixes and polish

A round of fixes from a hands-on trial run, so what you see matches what’s actually there:

Clip lists show real note counts instead of always reading 0.
Reading an empty clip slot returns a clean “no notes” result instead of an error.
Generated songs name every scene, even in longer arrangements — no more blank trailing scenes.
Automation read-backs point you to the right place when Live can’t display a bounced envelope, instead of looking like the write failed.
Consistent casing in generated scene and clip names.
Command shortcuts that match the tool names — arrangement list, note write, clip set-name, and more now work.
Mistyped options fail loudly instead of being silently ignored.

​Opt-in telemetry and vibrai feedback

​Switch between Session and Arrangement playback

​Clear a set’s clips, keep the rig

​Capture large sets in pieces

​vibrai update reliability

​Also

​Undo brackets tell the truth

​Rapid calls no longer trip the Python bridge

​A device delete can no longer remove the wrong device

​New projects are reproducible

​Genre lookups by name: ~6 s → milliseconds

​Compressor writes say when they settled for the nearest position

​Also

​Group changes into a single undo step

​Downloads moved to downloads.vibrai.com

​The version warning now says which side is behind

​Also

​Five drum parts stop copying the kick

​Break and fill steps follow the declared meter

​The installer no longer refuses while Live is running

​Breaking: three --json fields reported the wrong value

​Also

​Mixing advice, with the reasoning attached

​Look up what to reach for

​Bar lines land on your meter

​generate asks before duplicating your tracks

​Also

​Ask for a key and get it

​The Claude Desktop bundle, somewhere you can find it

​Automation is its own step

​Turn track numbering on and off

​Where a project file lands by default

​Fixed

​Songs that aren’t in 4/4

​Shape a sound, don’t just automate it

​Wizards that actually run

​Also new

​Fixed

​Before you upgrade

​A real mixer

​Colour

​Change one note, not the whole clip

​Loops that vary as they play

​Fixes

​Before you upgrade

​Bass that moves

​Melodic parts with rhythm and memory

​Harvested phrases you can reuse

​Everything in a section agrees on the chords

​Fixes

​Also new

​Clear-before-generate

​Automatic Max for Live bridge recovery

​Fixes

​Fixes

​Fixes

​Claude Desktop Skill packaging

​New guided wizards

​Fixes

​Session-view scene playback

​macOS installer + uninstall hardening

​.mcpb manifest fixes

​Automation you can trust

​Auto-numbered tracks

​Smaller installs, more reliable updates

​A new way to install: Homebrew

​A more reliable connection for AI assistants

​Fixes and polish

​Install, update, and uninstall — cleanly

​Drive Vibrai from your coding agent

​A smoother activation experience

​Fixes and polish

Opt-in telemetry and `vibrai feedback`

Switch between Session and Arrangement playback

Clear a set’s clips, keep the rig

Capture large sets in pieces

`vibrai update` reliability

Also

Undo brackets tell the truth

Rapid calls no longer trip the Python bridge

A device delete can no longer remove the wrong device

New projects are reproducible

Genre lookups by name: ~6 s → milliseconds

Compressor writes say when they settled for the nearest position

Also

Group changes into a single undo step

Downloads moved to downloads.vibrai.com

The version warning now says which side is behind

Also

Five drum parts stop copying the kick

Break and fill steps follow the declared meter

The installer no longer refuses while Live is running

Breaking: three `--json` fields reported the wrong value

Also

Mixing advice, with the reasoning attached

Look up what to reach for

Bar lines land on your meter

`generate` asks before duplicating your tracks

Also

Ask for a key and get it

The Claude Desktop bundle, somewhere you can find it

Automation is its own step

Turn track numbering on and off

Where a project file lands by default

Fixed

Songs that aren’t in 4/4

Shape a sound, don’t just automate it

Wizards that actually run

Also new

Fixed

Before you upgrade

A real mixer

Colour

Change one note, not the whole clip

Loops that vary as they play

Fixes

Before you upgrade

Bass that moves

Melodic parts with rhythm and memory

Harvested phrases you can reuse

Everything in a section agrees on the chords

Fixes

Also new

Clear-before-generate

Automatic Max for Live bridge recovery

Fixes

Fixes

Fixes

Claude Desktop Skill packaging

New guided wizards

Fixes

Session-view scene playback

macOS installer + uninstall hardening

`.mcpb` manifest fixes

Automation you can trust

Auto-numbered tracks

Smaller installs, more reliable updates

A new way to install: Homebrew

A more reliable connection for AI assistants

Fixes and polish

Install, update, and uninstall — cleanly

Drive Vibrai from your coding agent

A smoother activation experience

Fixes and polish