✅Release 3.2.10
Published to the Chrome Web Store on August 11, 2026
✨ Enhancements
Page Editor: added an advisory warning when a mod uses a built-in brick that only runs in the browser extension, so a mod that also runs on the Web App doesn't ship a brick that hard-fails there.
🐛 Bug Fixes
Bricks:
Convert Document: return a clear error instead of failing internally when the input document is missing.
Hardened built-in brick input schemas: reject non-finite, negative, or zero values for inputs that drive loops, polling deadlines, and cache expiry, and reject blank values interpolated into registration ids (which could silently overwrite another registration).
Templates: fixed template variables used with the
~concatenation operator or anistest being dropped from the rendering context.Page Editor:
Google Sheets: fixed the Google Sheets configuration picker.
JQuery Reader: fixed the Extract field showing "[object Object]" when the attribute is set from a variable or template.
Sidebar:
Fixed a temporary panel hanging on a loading spinner when its content arrived before the panel finished opening.
Fixed a rendered panel crashing while printing or with devtools open.
Fixed the "Widget hide-ui-modal already found on the page" error by replacing a stale modal root instead of failing.
Audio Capture:
Show a readable "requires Google Chrome or Microsoft Edge on a desktop computer" message instead of a raw browser error when recording tab or system audio on an unsupported browser.
Fixed audio capture start hanging silently when the transcription connection never opened or the API key was invalid — it now fails with an error.
Fixed a stale "Already capturing tab audio" error that could block the next recording after a capture ended abnormally.
Report a tab close, navigation, or the browser's native "Stop sharing" distinctly from a deliberate stop, and preserve the end reason across a background restart.
Honor discard-recording and fully release media tracks when a capture ends abnormally or its stop fails.
Reliability: background maintenance tasks (extension-version and team-trial checks, log cleanup) now use chrome.alarms so their schedules survive browser restarts and service-worker teardown.
Last updated
Was this helpful?