Ghost Fetch
Under maintenancePricing
Pay per usage
GHOST_FETCH_TELEMETRY_RAW=1 attaches the full raw fetch result — the same payload /v1/fetch returns, including the HTML body, response headers, final_url, decision trace, and base64 screenshot — to the request telemetry event under a raw_response field. Off by default; sanitized telemetry is unchanged (backward compatible).GHOST_FETCH_TELEMETRY_RAW and a valid custom GHOST_FETCH_TELEMETRY_DATASET_ID, so raw payloads (bodies, set-cookie headers, full URLs) never reach the shared default ghost-fetch-telemetry dataset that feeds Passive Context Profiles.GHOST_FETCH_TELEMETRY_DATASET_ID is now validated as an Apify Dataset id (17-char alphanumeric) or name (name / username/name); a malformed value warns and falls back to the default dataset instead of wedging writes. The dataset open is also no longer cached on failure.body is bounded by GHOST_FETCH_TELEMETRY_RAW_MAX_BYTES (default 6 MB, fits Apify's ~9 MB item limit); when truncated the event carries raw_response_truncated: true.pip install "cloverlabs-camoufox[geoip]" + python3 -m camoufox fetch official/150.0.2-alpha.26.rt:c captcha. cloverlabs FF150 → auto-solvable rt:i interstitial.fox_main_world_eval request paramcloverlabs/FF150 has no Juggler-scope isolation (single-world model). The flag set camoufox's allowMainWorld:True which is now inert; the mw: prefix it was meant to enable is parsed as a JavaScript label. The param has no observable effect on this build and is dropped from the request schema and the FoxOptions interface. See proxy-mcp v3.3.0 for the underlying world-model investigation and scripts/camoufox-world-probe.ts to verify on any installed build.
inPageFetch no longer hidden from page hooksinPageFetch() (src/fetch.ts:498) issues fetch() via page.evaluate to avoid Akamai poisoning of GET navigation. Under daijro/FF135 the eval ran in a Juggler scope, isolated from any page-installed window.fetch hooks. Under cloverlabs/FF150 it runs in the page's main world — pages that have hooked window.fetch (Akamai, PerimeterX) now observe the request. No correctness change; potential detection signal on high-tier WAFs.