FAQ

FAQ

Why Firefox and not Chromium?

Engine ownership. The anti-detect lives in C++ patches inside our own Firefox fork — not in injected JS that detectors can read. Chromium-based stealth browsers are wrappers around an engine they don't control; we control the whole stack, which also means we can fix what breaks (we've shipped fixes upstream to the Camoufox lineage ourselves).

How is this different from Camoufox?

Ghostfox is a fork of the Camoufox lineage with its own branding, a Rust MCP runtime, native captcha solvers, the debug cortex, receipts and recipes. Camoufox is the engine foundation we build on — and we track it, patch it, and contribute back (see PR #782).

What makes it "agent-native"?

Agents speak Model Context Protocol directly to the browser: 48 tools covering observation (page_a11y — including the native accessibility-tree source), action (click/type with receipts), evidence (recordings, diffs), determinism (recipes: record → replay without an LLM), and debugging (console/errors/network capture).

Do I need a GPU?

No. The captcha models (YOLOv8s, siamese, ddddocr OCR) run on CPU — production icon-clicks solve in ~0.5s on a plain x86_64 box. The optional vision-ensemble tools can call any vision-capable LLM, but the native solvers are fully local.

Is this legal?

Ghostfox is a testing and research tool. Anti-detect capabilities exist for legitimate automation and research the same way they do in every stealth browser; what you test with it is your responsibility. Don't use it against targets you don't have permission to test.

Self-hosted — what does that actually mean?

Your agent's identities, cookies, and sessions never touch a third-party cloud. No browser rent, no vendor lock-in: pip, npm, Docker, or build from source.

Something broke — where do I look?

The Troubleshooting page. If it's not there, open a Discussion — confirmed solutions get written back into the wiki.