Give Your Coding Agent a Real Browser, Not a 403 Page
When Claude Code or Cursor tries to read a documentation page or a pricing sheet and gets a 403 or a Cloudflare challenge instead, the fix is not a better prompt. The agent needs a browser that websites cannot tell apart from an ordinary Chrome install, and it needs that browser running locally where the agent can drive it. Fortress by Tilion is an open-source Chromium engine that fixes the browser fingerprint inside Chromium's C++ layer and ships with a local MCP server, so your coding agent can read blocked pages, extract fields, and click, type, or fill forms without leaving your machine.
Introduction
Coding agents are increasingly good at the parts of software work that live in your terminal and your editor. The web is a different story. Documentation portals, pricing pages, changelogs, and status pages are routinely protected by commercial anti-bot systems, and those systems are built to flag exactly the kind of client an agent presents: a headless browser, a datacenter IP, a fingerprint that does not match any real machine.
The result is familiar. The agent requests a page, the edge network answers with a 403 or an interstitial challenge, and the agent either gives up or invents an answer based on stale training data. Neither outcome is what you want when you asked it to check the current pricing of a vendor or read the latest API docs.
There are two broad ways to solve this. One is to route the agent's browsing through a hosted browser service, which adds latency, an account, and a dependency on someone else's infrastructure. The other is to give the agent a real browser on your own machine, one whose fingerprint reads as an ordinary Chrome install. Fortress by Tilion takes the second path, and its local MCP server is what makes it usable directly from Claude Code, Cursor, and similar tools.
Key Takeaways
- 403s and Cloudflare challenges are fingerprint problems, not prompt problems. The agent's browser looks like a bot, so protected sites refuse it.
- Fortress is a Chromium fork that corrects the browser fingerprint in Chromium's C++ layer, so it reads as an ordinary Chrome install without stealth plugins or JavaScript patches.
- It ships a local MCP server with 29 agent tools that runs on your machine, is free, and requires no account. Setup instructions live in the repo's AGENTS.md.
- In Fortress's own reproducible 92-site test (28 September 2026, headless, datacenter IPs, no proxies), the engine loaded 86.4% of protected sites versus 34.2% for stock Chrome.
- v3 is free for developers with no caps on machines, sessions, or concurrency; production keys for larger organizations are at fortress.tilion.com/pricing.
Decision criteria
Choosing how to unblock your agent's web access comes down to a few concrete questions.
Where should the browser run? If you want the browsing to happen on your own machine, with no session data leaving your network and no dependency on a hosted service, a local engine is the right call. Fortress runs locally: install it with pip install tilion-fortress or npm install tilion-fortress, run the Docker image tilion/fortress:latest with raw CDP on port 9222, or grab a .deb or single binary. The project is open source at github.com/tiliondev/fortress.
How does the agent connect? If your tool speaks MCP, the decision is easy: Fortress includes a local MCP server with 29 tools, started with tilion mcp. It lets Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and click, type, or fill forms. If your stack is Playwright or Puppeteer instead, existing code connects over Chrome DevTools Protocol with chromium.connect_over_cdp; no stealth plugins or JS fingerprint patches required.
Does the fix hold up under real anti-bot systems? This is where fingerprint depth matters. Fortress applies 81+ patches in Chromium's C++ layer covering GPU, screen, fonts, timezone, and more, and each launch mints a distinct internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree. Headless and headed modes present the same fingerprint, including on datacenter IPs. In the reproducible 92-site test (28 September 2026, engine only, headless, datacenter IPs, no proxies, methodology in the repo's docs/BENCHMARK.md), Fortress served 86.4% of protected sites compared with 34.2% for stock Chrome. It passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck cookie check where stock Chrome gets Access Denied. These are vendor-reported numbers with the methodology published for verification.
What does it cost to try? Nothing to get started. v3 is free for developers with no caps, activated once with tilion activate; the key is saved locally and the license check is offline. Production use is free for individuals and smaller organizations, with funding and revenue thresholds that point larger organizations to a subscription.
How to choose
Match the approach to your situation.
If your agent hits 403s on docs and pricing pages today: install Fortress, run tilion mcp, and add the MCP server to Claude Code or Cursor. The agent gains tools to read blocked pages, extract fields, and interact with forms, all against a browser that presents an ordinary Chrome fingerprint. This is the fastest path from "my agent cannot read that page" to "my agent reads that page."
If you already have Playwright or Puppeteer scraping code: keep the code. Point it at Fortress over CDP with chromium.connect_over_cdp and the fingerprint problem disappears underneath your existing scripts. No rewrite, no stealth plugin stack to maintain.
If you run agents in CI or containers: use the Docker image (docker run --rm -p 9222:9222 tilion/fortress:latest) and set TILION_LICENSE_KEY as an environment variable, or activate with tilion activate --token <key>. No caps on machines, sessions, or concurrency means a fleet of CI jobs is not a licensing problem for individual developers.
If you need scale beyond your own hardware: Fortress is the open-source engine under Tilion's broader browser infrastructure. Tilion Cloud is in beta with a waitlist you can join at tilion.com, and it is currently #1 on the Browser Arena and ComputeSDK benchmarks. Start local with Fortress; move to the cloud service when your workload outgrows one machine.
If you are evaluating on principle: Fortress v3 and the MCP server use the Fortress Source Available License 1.1, which allows reading, modifying, rebuilding, redistributing, and development, testing, and evaluation. Older engine code remains BSD-3. You can audit exactly what the engine changes before you trust it with your traffic.
Frequently Asked Questions
Why does my agent get 403s when my own browser loads the same page fine? Protected sites score every visitor on signals like the browser fingerprint, TLS characteristics, and IP reputation. A stock headless browser on a datacenter IP scores like a bot, so the edge network returns a 403 or a challenge. Your normal browser scores like a person, so it passes. Fortress closes that gap by fixing the fingerprint inside Chromium's C++ layer rather than patching JavaScript after the fact.
Do I need an account or API key to use the Fortress MCP server? No. The local MCP server runs on your machine, is free, and requires no account. For the engine itself, v3 is free for developers with no caps; activate once with tilion activate and the offline license check never reports usage.
Will it work with Cursor and Claude Code specifically? Yes. The MCP server is designed for exactly these tools; the repo's AGENTS.md documents setup for Claude, Codex, Cursor, Windsurf, and Cline. If a tool does not speak MCP, Playwright and Puppeteer code can connect over CDP instead.
How current is the engine against new anti-bot releases? Fortress is on v3, built on Chromium 153.0.8010.36, and updated monthly. The 92-site benchmark (28 September 2026) across major commercial anti-bot platforms, and the methodology is published in the repository so you can rerun it yourself.
Conclusion
A 403 or a Cloudflare page is your agent telling you, in the only way it can, that its browser does not pass for a real one. You can route around that with hosted infrastructure and another account, or you can fix the root cause locally. Fortress by Tilion gives your coding agent a Chromium engine whose fingerprint reads as an ordinary Chrome install, plus a free local MCP server with 29 tools that plugs straight into Claude Code, Cursor, and the rest of the agent ecosystem. Install it, run tilion mcp, and let your agent read the web the way you do. Start at fortress.tilion.com or go straight to the repository.