What Is Ulixee Hero? – Definition and How It Works
Learn what Ulixee Hero is, how full-stack emulation differs from patching a browser, and what its network-layer approach buys and costs.
Ulixee Hero is an open-source browser-automation project, previously known as SecretAgent, built on the position that hiding automation means emulating a browser through the whole stack rather than patching one layer of it.
1. The Full-Stack Position
Most stealth work targets JavaScript: rewrite the properties a fingerprinting script reads and hope nothing else gives it away.
Hero's argument is that a session is identifiable well below JavaScript. Before any script runs, a site can read the TLS handshake — cipher suites, extensions, and their ordering, summarised as a JA3 or JA4 fingerprint — and the HTTP/2 settings frame, which varies between browser builds in ways a client library rarely reproduces.
A patched browser that fixes navigator.webdriver while presenting a Python client's TLS signature has contradicted itself before the page loaded.
2. What It Emulates
Hero aims to present a coherent identity at each layer: the TLS handshake, HTTP/2 framing and header ordering, the browser's DOM and JavaScript surface, and human-plausible interaction timing for input.
The project has historically paired this with a test suite of its own for measuring how well a session matches a real browser, on the reasoning that emulation claims need a scoreboard rather than a feature list.
3. What the Approach Costs
Emulating a browser across every layer is a large ongoing commitment. Each upstream browser release changes some of what is being emulated, and every gap between the emulation and the real thing is a potential signal.
The practical consequences are a smaller ecosystem than the mainstream automation libraries, a distinct API rather than a drop-in replacement for Puppeteer or Playwright, and a dependence on how actively the project tracks browser releases. Check the project's recent activity before committing to it.
4. Where the Idea Matters Regardless
Even for teams that choose a different tool, the underlying point is worth carrying: detection happens at several layers, and the weakest one decides the outcome.
That is why a stealth plugin does not help when the TLS signature says Python, why a perfect fingerprint does not help from a flagged address, and why a real browser is the most reliable way to present a consistent stack — it produces every layer natively instead of reproducing it.
5. Summary
Ulixee Hero is an open-source automation project that emulates a browser across TLS, HTTP/2, DOM, and interaction layers rather than patching JavaScript alone. The approach addresses signals that in-page patching cannot reach, at the cost of a large maintenance surface and a smaller ecosystem. Its central claim — that the weakest layer decides detection — holds regardless of which tool you pick.