Skip to content

v0.6.2 — Guarded runtime UI control

Choose a tag to compare

@2bbb 2bbb released this 14 Oct 13:26
· 12 commits to main since this release

Runtime UI control

  • Add maxforge_read_runtime and maxforge_send_message to the Max-owned HTTP service. One maxforge object remains sufficient; no MCP, helper objects, or separate Node installation.
  • Support a deliberate subset of messages for 28 standard Max/live.* UI classes. Read values without output; distinguish numeric input, bang, class-specific silent set, and typed selector/atoms.
  • Guard every request with patch/scope/instance identity, inspected object identity, and a structure token. Unmanaged targets require explicit opt-in. Native acknowledgements distinguish completed, rejected, and unknown outcomes; sends are never automatically retried.
  • Keep volatile values, formatted numeric display text, and subpatch editor session state out of structural editing. Fix empty outlet comments being mistaken for DSL edits.
  • Update the maxforge-live skill, class-specific reference, generated help, and reproducible host acceptance script.

Validation and limits

The pre-release suite covers 431 TypeScript tests, native CTest, coverage thresholds, installed npm package validation, and Max 9.0.4 on Apple silicon: 32 UI configurations / 123 messages, actual downstream counters, silent reads/sets, cross-patch and nested routing, invalid requests, unchanged DSL, and save/reopen. macOS and Windows externals are built and tested in CI. Windows host loading, Intel host execution, Ableton Live automation, and DSP/audio output are not covered by the macOS host test.

The macOS external is universal arm64/x86_64, Developer ID signed and Apple-notarized. Max 9 and its bundled Node 20+ are required. No Node runtime is bundled. Install the complete versioned Max package ZIP and verify its matching SHA-256 file; do not replace only the native binary.

Install/update the agent instructions with npx skills add bbb-max-externals/maxforge --skill maxforge-live. Updating the skill alone does not replace the Max package or remove legacy MCP configuration. Ask the agent to perform the documented setup/migration workflow when needed.