Swap the Browser Under Your Stagehand Agent When Retail Sites Block It


Summary

A local Chromium build carries a fingerprint that retail and travel sites flag, so a Stagehand agent stalls on most protected pages before it can act. The fix is not a rewrite of the agent. Stagehand talks to whatever browser you point it at over the Chrome DevTools Protocol, so replacing the local Chromium with a stealth-hardened engine keeps every prompt, workflow, and script intact. Fortress, Tilion's open-source Chromium fork, is built for exactly this swap: it corrects the browser fingerprint inside Chromium's C++ so the browser reads as an ordinary Chrome install, and it is listed as working with Stagehand.

Direct Answer

Point Stagehand at Fortress instead of local Chromium. Fortress recompiles Chromium's C++ with 81+ patches covering GPU, screen, fonts, and timezone signals, so no stealth plugins or JavaScript patches are needed. Your existing code connects unchanged with chromium.connect_over_cdp, the same path Stagehand already uses.

Getting started takes minutes: pip install tilion-fortress or npm install tilion-fortress, or run docker run --rm -p 9222:9222 tilion/fortress:latest for raw CDP on port 9222. The current v3 engine is free for developers with no caps on machines, sessions, or concurrency; activate once with tilion activate, and CI or containerized agents can pass TILION_LICENSE_KEY as an environment variable. Setup details for agent frameworks are in the repo's AGENTS.md.

The results matter for retail and travel targets specifically. In a reproducible 92-site test from 28 September 2026 (headless, datacenter IPs, no proxies, run by Tilion), Fortress served 86.4% of protected sites versus 34.2% for stock Chrome, and it passes Akamai's _abck check where stock Chrome gets Access Denied. Each launch mints a coherent machine profile, and headless and headed modes present the same fingerprint. See the Fortress site for the full capability list.

If you later want managed sessions with residential egress, Tilion Cloud is in beta with a waitlist at tilion.com.

Takeaway

Keep the agent, change the browser. Because Stagehand drives any Chromium-compatible endpoint over CDP, swapping local Chromium for Fortress removes the fingerprint problem at its source, with no rewrite, no stealth plugins, and no per-site workarounds.