Lavra v0.7.6 Release Notes

Release date: 2026-04-20

Critical bug fixes

Multi-bead review no longer silently skips code analysis

When /lavra-work processed multiple beads in parallel, the mandatory /lavra-review step after each wave appeared to run but wasn’t actually analyzing any code. Agents dispatched, time was spent, but no issues were caught. Beads then committed and closed with the review gate bypassed.

This only affected the multi-bead path. Single-bead review worked correctly.

Review diff now captures uncommitted working tree changes

The fix ensures /lavra-review sees all changes produced by parallel subagents, even though those changes haven’t been committed yet when review runs.

Improvements

Hooks auto-update across all projects after a global install

Updating Lavra globally (bunx @lavralabs/lavra@latest) now propagates hook fixes to every existing beads project automatically. On the next session start in any project, check-memory.sh detects the newer global version and re-copies hooks. No need to run the per-project installer for each project.

Previously, once hooks were installed in a project, they stayed at that version forever regardless of global updates.

Per-project installer avoids duplicating global files

When installing into a project that already has Lavra globally, the installer now checks whether the global install is current. If it is, only hooks are updated — commands, agents, and skills stay global. No more stale local copies.

If the global install is older than the installer, it warns and gives you three options: update global first (recommended), install a full local copy anyway, or update hooks only.

Installer banners now show the correct version

All platform installers used to display a hardcoded version string that was frequently out of date. They now read the live version from the plugin manifest automatically.

Upgrading

bunx @lavralabs/lavra@latest

No breaking changes.