What is camofox-browser?
camofox-browser is an anti-detection browser server for AI agents, powered by Camoufox, a Firefox fork with fingerprint spoofing at the C++ level. It is built by the team behind jo, a personal AI agent. The README explains the problem: agents need to browse the real web, but Playwright gets blocked and headless Chrome gets fingerprinted.
Camoufox patches Firefox at the C++ implementation level, spoofing values such as navigator.hardwareConcurrency, WebGL renderers, AudioContext, screen geometry and WebRTC before JavaScript sees them. camofox-browser wraps that engine in a REST API with accessibility snapshots instead of raw HTML, stable element refs such as e1 and e2 for clicking, and search macros for common sites.
Other listed features include session isolation with separate cookies and storage per user, Netscape-format cookie import, proxy and GeoIP routing, file upload, download capture, structured extraction with a JSON Schema, opt-in session tracing, and OpenAPI docs at /openapi.json. The browser launches lazily and shuts down when idle to keep memory near 40 MB. You can run it with npm start on port 9377 or deploy with Docker, Fly.io or Railway. The README notes anonymised crash telemetry.
Key capabilities
- A REST API for browsing with a Camoufox (Firefox fork) engine.
- Accessibility snapshots that the README says are about 90% smaller than raw HTML.
- Stable element refs for reliable clicking and typing.
- Per-user session isolation, cookie import and proxy with GeoIP routing.
- Search macros such as @google_search and @youtube_search.
- Docker, Fly.io and Railway deployment and auto-generated OpenAPI docs.
Where camofox-browser fits
camofox-browser fits into agent workflows that need to search websites, interact with forms, reuse authenticated browser sessions or retrieve documents encountered during browsing. Search macros cover common sites, while the transcript endpoint uses yt-dlp when available and otherwise falls back to a slower, less reliable browser-based method.
Before deployment, teams should test their target sites and authentication flows, configure network binding and route-specific access keys, and review stored session data and telemetry settings. Container builds require the documented binary-download workflow rather than a direct Docker build. Remote visual login also requires deliberate VNC binding and password configuration.
Install
npm install @askjo/camofox-browserReviews of camofox-browser
Be the first to share your experience with camofox-browser.
Write a review
Loading review form…
Alternatives to camofox-browser
agent-browseragent-browser is a native CLI with skills for AI agents to navigate pages, fill forms, extract data and take screenshots using accessibility-tree snapshots.
MCP Playwright ServerPlaywright MCP lets AI clients automate Chrome, Firefox, WebKit and Edge through accessibility snapshots instead of screenshots.
MCP Puppeteer ServerArchived MCP reference server that lets AI clients drive a Puppeteer browser: navigate, click, fill forms, take screenshots and run JavaScript.