CamoFox Browser: anti-detection browser for AI agents
camofox-browser
A REST server and CLI on Camoufox: an agent opens pages with a spoofed browser fingerprint and reads them as an element tree
- 443 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Fingerprint spoofing exists so that sites recognize automation less well: many platform rules forbid it and the account may be blocked
- Persistent profiles, cookies and the credential vault give the agent access to your site logins
- The `reddit` skill publishes posts and comments from your account
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/camofox-browserDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Fingerprint spoofing exists so that sites recognize automation less well: many platform rules forbid it and the account may be blocked
- Persistent profiles, cookies and the credential vault give the agent access to your site logins
- The `reddit` skill publishes posts and comments from your account
This is third-party code. Review the repository files before installing.
What it does
CamoFox Browser is a TypeScript server (Node.js 22 or newer) that wraps Camoufox, a Firefox fork that spoofs the device fingerprint at the engine level. An agent works with it through the REST API or the `camofox` CLI: it opens a page, gets an accessibility snapshot with labels such as `e5` and `e3`, and clicks or types by those labels. The snapshot is shorter than raw HTML or a screenshot, so it uses fewer tokens. Each `userId` gets a separate browser context with a persistent Firefox profile: cookies, localStorage and IndexedDB survive between runs. By default there are limits of 50 sessions and 10 tabs per session. There are 8 regional presets (language, time zone, geolocation), session-level proxies, 14 search macros (Google, YouTube, Amazon, Reddit and others), structured extraction by a JSON schema, browser console capture and Playwright traces. The credential vault encrypts entries with AES-256-GCM, and the `--inject` flag passes a password straight to the browser so the agent never sees it. The repository ships agent skills installed with `npx skills add redf0x1/camofox-browser`: `camofox-browser`, `camofox-cli`, `dogfood`, `gemini-image` and `reddit`. For MCP clients the author points to a separate project, CamoFox MCP. The README labels the project a Preview release.
Who it is for. Agent and automation developers who need a controllable browser with persistent profiles and a fingerprint that differs from stock Playwright.
Good fit when
- An agent has to visit sites where plain Playwright or Puppeteer is recognized as automation
- A login has to persist between runs so the agent returns to the same session
- Checking pages from different regions needs a language, time zone and geolocation from a ready preset
- Page data is needed as JSON by a given schema, without running an arbitrary script
- A web app test scenario needs the `dogfood` skill and a recorded trace for the agent
Not a fit when
- The task is solved by plain Playwright: fingerprint spoofing adds memory use and complexity for nothing
- The site bans automation in its rules or API: fingerprint spoofing breaks the terms and leads to an account block
- The server must sit on an open network without a key: with a non-loopback `CAMOFOX_HOST` a `CAMOFOX_API_KEY` is mandatory
- A stable API is required: in Preview status response formats and local state may change between minor versions
Example request
Open https://example.com in the camofox browser, take an accessibility snapshot, find the search form and type «MCP» into itLimitations
Node.js 22 or newer and at least 2 GB of memory are required; for production load Linux is recommended. The Camoufox engine is downloaded during `npm install`, and the installation fails if the download or validation fails.
The server listens on loopback by default. For other `CAMOFOX_HOST` addresses `CAMOFOX_API_KEY` is required, and `CAMOFOX_AUTH_MODE=disabled` is meant only for a closed network of agents. Access to private addresses and metadata is enabled by `CAMOFOX_ALLOW_PRIVATE_NETWORK`. The Preview release does not guarantee a stable API or migration of local state on upgrade.
How to disable. Stop the server, remove the package with `npm uninstall -g camofox-browser` and delete the `~/.camofox` directory with profiles and the credential vault. Remove the agent skills from its skills folder.
FAQ
How do I install CamoFox Browser?
Run `npm install -g camofox-browser`, then `camofox open https://example.com`. The CLI starts the server itself. To build from source, clone the repository and run `npm install`, `npm run build` and `npm start`.
How do I add the CamoFox skills to Claude Code?
Run `npx skills add redf0x1/camofox-browser` and choose the skills you need. For Claude Code `SKILL.md` lands in `.claude/skills/camofox-browser/`, for Cursor, Copilot and Codex in `.agents/skills/`.
Is there a CamoFox MCP server?
Not in this repository: a separate project, CamoFox MCP (redf0x1/camofox-mcp), covers Claude, Cursor and VS Code. This repository holds the REST API, the CLI and the skills.
How does an agent log in without seeing the password?
Through the credential vault: `camofox auth load gmail --inject --user` passes the data straight into the browser. Entries are encrypted with AES-256-GCM using an Argon2id key, and the password never reaches stdout.
Which port does the server use?
`9377` by default, changed with the `CAMOFOX_PORT` variable. The address `127.0.0.1` is the default; for Docker it is changed to `0.0.0.0` together with `CAMOFOX_API_KEY`.
Discussion
No questions or reviews yet.
Related
CLI toolsAnti-detect browser profile manager with a fingerprint, cookies and proxy per profile. A built-in MCP server connects agents.
A separate browser for agents with a skill and MCP: Claude Code and Codex work in your logged-in accounts, and every session is recorded for replay
A Chromium with engine-level device fingerprint spoofing and an MCP server that lets an agent drive it through Playwright
A Rust browser engine without Chromium, with its own TLS fingerprint and V8; the MCP server gives agents pages and protection checks.
Agent browser on direct CDP without Playwright: login profiles, a CLI, an MCP server and recording workflows into a skill
A web research skill: SearXNG searches, Camofox reads pages and CloakBrowser opens sites that check their visitors
README in short
The README explains engine-level fingerprint spoofing and compares the server with Playwright, then covers the Preview status, running from source and through npm, CLI commands, the REST API, environment variables, Docker and deployment on Fly.io, Railway and Render. MIT license.