Released 2026-06-06. Published playgrounds can now read the URL of the page they're on — its query parameters and hash — which previously weren't visible inside the playground sandbox.
Added
flowfn.location.query— the page's query parameters as an object. For a visitor onyour-site.flowfn.com/?q=abc, your code readsflowfn.location.query.qas'abc'.flowfn.location.searchgives the raw query string.flowfn.location.hash— the URL fragment (e.g.#support). It's also applied towindow.location.hashbefore your code runs, so existingwindow.location.hashcode and in-page#anchorlinks work.- Automatic deep-link scrolling — opening a playground with a fragment that matches an element id (e.g.
/#pricingwith a<section id="pricing">) scrolls that section into view on load. No code needed.
Why
A playground runs in a sandboxed iframe with its own internal address, so window.location.search inside it was always empty and the page's hash never reached your code. flowfn.location forwards both in. See the Playground SDK reference.