Aesel 0.8.15: ac check runs a piece and prints its errors; the launcher stops forcing claude master
- ac check <piece.mjs | @handle/slug> plays a piece in headless Chrome on aesthetic.computer (a local file is served in place of a scratch piece, bypassing the site's service worker), taps and presses space, and prints every page error, console.error and AC's own caught failures ("🎨 Paint failure…" warnings, with the real error and location), once each with a count. The bumblebee parsed and published but threw in wipe() every frame; this finds it before and after. - Pro's loop is now write → ac check → fix until ✓ → publish → ac check the published piece; the context map says API functions exist only as parameters (the bumblebee's helper called a wipe it never received). - The launcher passed --backend claude on every launch, so the TUI ignored the provider you last chose and /update came back on Claude. It now passes a backend only when asked; a first launch starts on the hosted provider. - Aesel writes agent_type "aesel" now that the fleet's menubars read it; prox prints session·aesel and prox:aesel:… addresses. - Clicking the update banner runs /update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>