Isolation layers
Cookies, storage, cache, proxy per profile
IFox9 · Antidetect browser · Claude / Cursor / Codex
Antidetect browser for multiple accounts
Separate your profiles. Automate browser tasks with AI.
Manage store and client accounts in separate IFox9 browser profiles, each with its own cookies, login sessions and proxy settings. Connect Claude, Cursor or Codex through local MCP to read pages, fill forms and download reports. Review important changes before submitting them.
Free: 20 profiles · 2 seats · Windows / macOS · Local MCP
Browser runtime
Stable desktop browser kernel
MCP clients documented
Claude, Cursor, Codex, and more in docs
Setup
Choose profile → connect → run & review
Manage multiple stores and client accounts
Give each store or client account its own browser profile, cookies and proxy settings. Check that you have the right profile before opening a dashboard or downloading a report.
AI browser automation
Use your AI assistant to read product details, fill forms, take screenshots or download files in a selected profile. Review the result before updating a listing or sending a message.
Organize profiles for your team
Group profiles by store, market or responsibility so teammates can find the right account. Let AI assist with repetitive tasks while your team reviews important changes.
One workspace for identities, teams, and automation
Keep browser environments separate while your people and AI tools work through explicit, reviewable controls.
Read the browser profile isolation guide →01Profile isolation
Profile isolation
Each profile keeps its own cookies, local storage, cache, and profile settings to reduce accidental account-state mixing.
Cookie: SeparateCache: IsolatedStatus: Ready
02Network identity
Proxy and network
Assign HTTP, HTTPS, or SOCKS5 proxies per profile so the network identity matches the intended workflow.
HTTP / HTTPSSOCKS5 ProxyRoute: Isolated
03Team controls
Team permissions
Assign profiles by responsibility without handing collaborators original passwords, with clear revocation boundaries.
Role: MemberGrant: ScopedAudit: Enabled
04Standard MCP
AI browser control
Use MCP to target the exact profile, page, and snapshot, starting with read-only tasks and reviewable automation.
Transport: LocalTarget: ExactReview: Human
Connect the AI clients you already use
Use the Model Context Protocol with Codex, Claude, Cursor, WorkBuddy, and other clients. Bring your own model access and third-party accounts.
Read the AI quickstart →Codex
OpenAI coding agent
Claude
Official desktop
Cursor
Direct IDE MCP
WorkBuddy
AI workspace
Doubao Work
Guided connection
Gemini CLI
Google native
VS Code
Editor ecosystem
Hermes Agent
General agent
Start an AI browser task in 3 steps
A standard workflow that works without brittle reverse engineering.
01
Choose a profile
Create or select the exact IFox9 browser profile, then confirm its proxy and signed-in state.
02
Connect your assistant
Configure a supported client in API & MCP, restart it, and test the connection.
03
Run and review
Begin with a read-only task, check the result, and keep consequential submissions under human review.
IFox9 / Pricing
Pricing →Room for your next workflow.
From individual profiles to team workspaces. Compare limits and billing periods before you choose.
DESKTOP APP
Choose your platform
Get IFox9 for Windows x64, macOS Apple Silicon, or macOS Intel.
Verifying the latest release manifest…