v0.2.0 — Bitwig 6.1.4 / MCP 2

Bitwig 6.1.4 and MCP 2

Experimental / Alpha. Use a disposable project and keep backups.

Changes and compatibility

• Private Grid/modulator bindings now target Bitwig 6.1.4 / API 25 and the exact loaded host-JAR SHA-256 77a50264156a9f79c925fa85e0456720ce157bfa10e2503d6049e2f733af4ba6. This replaces 6.1.3 private bindings; it is not dual-version support. Existing 0.1.2 artifacts remain unchanged.
• Includes the asynchronous combined stop/seek fix and explicit tracks.select dispatch semantics. Selection reports dispatched / not_observed, not fabricated completion; inspect the real UI and any auto-arm effect.
• Migrates the thin adapter to MCP SDK 2.3+, compatible with Arch's current system package. Python remains 3.11+; dependencies are mcp>=2.3.0,<3 and pydantic>=2.12,<3. No SDK 1 runtime shim or bundled private environment.
• The 45 dotted tool names, Bitwig RPC schemas, strict validation and known error envelopes remain. Unexpected uncaught adapter exceptions now surface as MCP JSON-RPC errors; never treat them as permission to retry.
• Updates README, installation/upgrade commands, public guides and the portable agent skill for this release.

Install or upgrade

Choose one route and keep Python and the extension matched:

uv tool install bitwig-agent==0.2.0
bitwig-agent-install

AUR metadata notice (2026-10-27): The public Git repository and .SRCINFO contain 0.2.0-1, but the AUR RPC/website still reports 0.1.2-1. The reason is not established and index synchronization is not verified. Prefer the PyPI route above until the indexed version updates; do not force an SDK 1 dependency downgrade.

On Arch, review and install the bitwig-agent AUR recipe, then explicitly copy the system asset as your normal user:

yay -S bitwig-agent
bitwig-agent-install --extension /usr/share/bitwig-agent/BitwigAgent.bwextension

Reload the controller after replacing its extension. bitwig-agent-install --mcp-config only prints client configuration; merge it deliberately. The installers do not start Bitwig, enable controllers, upgrade the proprietary host, or register a skill.

The wheel, sdist and extension are a matched set. Verify them with the attached SHA256SUMS. The checksum manifest is an integrity check, not independent signing or native acceptance. PyPI and AUR publication are separate from this GitHub release; check the registry version before using registry-based commands.

Verification and limits

• MCP 2.3 source checks: 1,161 Python tests, 45 matching Java/MCP tools and 50 example roundtrips, including invalid-input/no-dispatch and unknown-outcome preservation. 14 Java test mains also passed during release preparation.
• Final wheel and no-cache-built sdist consumers passed on Python 3.11 and 3.14. Isolated persistent uv and cached uvx commands, MCP discovery and temporary extension copies passed. An SDK 1.29.1 external client interoperated with the newly installed SDK 2 server through a disposable loopback peer; no native-host calls were made.
• Official disposable Arch container: clean build, incremental rebuild, 1,161 tests per build, installed CLI/MCP consumer, extension byte comparison and all 83 owned files verified. Namcap reported no errors; retained warnings misidentify installed Python/project symbols as missing dependencies, while the installed consumer and file checks succeeded.
• Independent release review found no actionable defect. Gitleaks found no credentials in the staged delta, actual release archives or all 29 reachable commits. This is scoped screening, not a guarantee that all sensitive content is detectable.
• The initial Arch candidate's SDK 1 dependency failure and a disposable probe's incorrect envelope assertion remain recorded; neither was hidden as an all-attempts-pass result.

The 6.1.4 musical/UI/render/save-reopen evidence in VERIFICATION.md belongs to recorded pre-release candidates and retains failed cases and coverage limits. The release extension differs from the last natively exercised candidate only in its version literal among uncompressed entries. This publication round did not rerun Bitwig or establish new native, audio, Undo, all-module or cross-platform acceptance. No primary compositor, user project, persistent local tool installation, global extension or MCP configuration was changed.