optional browser-rendered fetch for JS-heavy pages in remote ingest?
Author: feder-crCreated Jun 28, 2026Updated Jul 1, 2026
the remote ingest path (crawler_loader / remote loaders) fetches over http, so url sources that render their content with js come back mostly empty. would an optional browser-backed loader be useful for those, one that renders the page before extraction? it'd be a python playwright wrapper over a patched firefox with a realistic fingerprint, opt-in so the default http path stays unchanged. happy to prototype a loader against the remote parser if there's interest, otherwise no worries.
Source: arc53/DocsGPT