Viv Claude Code Plugin v0.12.0

Install latest from GitHub · Install v0.12.0 from GitHub · README

---

Added

• Shell command viv-plugin-get-monorepo-map for retrieving the monorepo map. This is needed because the map file is now stored outside the plugin files, as noted below.
• Shell command viv-plugin-version for retrieving the version of the plugin currently running.

Changed

• Move the monorepo map out of the plugin files and into the larger Viv monorepo (at docs/.llm/monorepo-map.md). The plugin now uses the map file included in its monorepo copy. Previously any structural change to the monorepo necessitated a new plugin release, because the plugin's map file had to be updated in turn. With the map file now being external to the plugin, monorepo changes do not affect plugin versioning.
• Rewrite all plugin docs to route monorepo navigation through the map, rather than hardcoding monorepo paths.
• Update /viv:sync to detect when the plugin you're actually running is older than the latest version Claude Code has downloaded into its cache. This catches a known Claude Code bug where new versions get downloaded but the old one keeps running until the cache is manually cleared.
• Bump the minimum Claude Code version to 2.1.85 (for the if-filter hook syntax on which the plugin relies).
• Document WSL 2 as the supported Windows path. The plugin's bash-based utility commands don't run reliably under native Windows shells, due to open upstream issues in Claude Code's plugin infrastructure.

Removed

• monorepo-map case from viv-plugin-get-plugin-file. Agents now use viv-plugin-get-monorepo-map instead.

Fixed

• A failed fetch via viv-plugin-fetch-monorepo wiped the existing monorepo copy.
• /viv:build failed on its first tool call because skills/build/SKILL.md referenced viv-plugin-get-doc, which was renamed to viv-plugin-get-plugin-file in 0.11.0.
• viv-plugin-install-sublime-package skipped dotfiles when copying source into the install directory, so .no-sublime-package never reached the destination. Also, reinstalls layered new content over previous installs without clearing stale files first.
• Auto-approval hooks matched as substrings, so a compound command like rm -rf ~ && viv-plugin-orient could still be auto-approved.
• Path validation in viv-plugin-read-monorepo-file and viv-plugin-explore-monorepo was lexical only, so a symlink under $MONOREPO_DIR pointing outside the sandbox would be silently followed.
• State files containing valid JSON that wasn't an object (lists, scalars, null) caused uncaught Python tracebacks in various plugin shell commands.

Viv VS Code Extension v0.11.1

Install latest from Marketplace · Install v0.11.1 from GitHub · README

---

Changed

• Align bundled color themes with corresponding color schemes from the Viv Sublime Text package.

Viv Compiler v0.12.1

Install latest from PyPI · Install v0.12.1 from PyPI · README · Compiler Reference

---

Fixed

• Newlines inside strings were parsed but not actually included in the compiled string expression. Now they are rejected with an error.

Viv VS Code Extension v0.11.0

Install latest from Marketplace · Install v0.11.0 from GitHub · README

---

Added

• Autodetection of an existing viv-compiler installation even when the extension's configured Python interpreter doesn't have it.
• Troubleshooting section in the README covering the case where the extension can't find viv-compiler and the user needs to set viv.pythonPath manually. Editor links to this when applicable.

Changed

• Streamline compiler-installation flows.
• Bump compatible compiler version to 0.12.

Viv Sublime Text Package v0.11.0

Install latest from GitHub · Install v0.11.0 from GitHub · README

---

Changed

• Invoke py -3 (the Python launcher) instead of python on Windows (more reliable).

Viv JetBrains Plugin v0.10.0

Install latest from Marketplace · Install v0.10.0 from GitHub · README

---

Added

• Autodetection of an existing viv-compiler installation even when the plugin's configured Python interpreter doesn't have it.
• Troubleshooting section in the README covering the case where the plugin can't find viv-compiler and the user needs to change the Python interpreter setting manually.

Changed

• Streamline compiler-installation flows.
• Bump compatible compiler version to 0.12.

Fixed

• Update-failure notification incorrectly titled "Viv compiler installation failed" (now correctly says "Viv compiler update failed").

Viv Compiler v0.12.0

Install latest from PyPI · Install v0.12.0 from PyPI · README · Compiler Reference

---

Added

• python line in --version output, carrying the absolute path of the Python interpreter running the compiler (allows editor plugins to auto-detect which interpreter to invoke).

Changed

• Restructure --version output to one machine-parseable <key> <value> field per line, replacing the previous stylized multi-line format.

Viv JetBrains Plugin v0.9.10

Install latest from Marketplace · Install v0.9.10 from GitHub · README

---

Added

• Signed plugin distribution.

Fixed

• The plugin's What's New tab was not updating to show changes.

Viv Compiler v0.11.2

Install latest from PyPI · Install v0.11.2 from PyPI · README · Compiler Reference

---

Added

• Validation check rejecting references to special roles (@this, @hearer) in casting pools.

Fixed

• The references field on wrapped effects and reactions omitted the @hearer and @this special roles, but these are required to be present at runtime.

Viv Sublime Text Package v0.10.0

Install latest from GitHub · Install v0.10.0 from GitHub · README

---

Added

• README instructions for applying a Viv color scheme to .viv files only.

Changed

• Rename bundled color schemes directory from themes/ to schemes/ to align with Sublime Text's terminology.