v0.20.0 — The Render Pass: rescue blocked & JavaScript-rendered pages

Highlights

• Failed page imports now rescue themselves. When a URL comes back blocked, blank, or JavaScript-rendered, Alchemy retries it in a hidden WebKit render pass — the real browser it already ships — and extracts the settled page. All local: no scraping service, no API key, no URL ever leaves your machine. Pages that used to import as errors or a sentence of boilerplate now arrive whole (a Cerebras blog post went from 48 characters to 22,700; Apple's Human Interface Guidelines pages from ~260 to 4k–55k each).
• Rescue reaches add, refresh, and scheduled re-syncs alike. Any source that flows through URL import — a fresh add, a manual refresh, a report's re-sync — inherits the render pass, so old errored sources heal on their next refresh.
• Cleaner captures. The render pass scrolls the page (including inner scroll panes) to trigger lazy-loaded content, drops full-screen consent overlays, and pulls author and publish date into a provenance line at the top of the source.
• Sites that need rendering are remembered. Once a domain wins by rendering, later imports from it skip straight to the render pass instead of re-failing the quick fetch first; a domain that starts working normally again is forgotten (30-day freshness).

Notes

• Rescue is macOS-only for now and runs automatically — no setting to enable.
• Login walls, bot challenges (CAPTCHA/Cloudflare), and empty search results are left as-is rather than worked around; those stay honest errors or thin results.

Full Changelog: v0.19.0...v0.20.0