The anti-detect browsermade for AI agents

Persistent identities. Fail-closed proxy controls. Built for Claude Code and Codex.

Native control.
Less overhead.

Give Claude Code and Codex exactly the page context they need.

Research profileConnected via MCP

Claude Code

Codex

Claude Code / Codex

Inspect the sign-in form in this profile.

Illustrative form fields and action diff

Scoped snapshot ready

Real work. A consistent identity.

One browser identity, from first action to final handoff.

Pick up where you left off

Collect sources across sessions with the same persistent identity.

A human when it matters

Browser workflows can require CAPTCHA or 2FA. Human verification remains part of the process; handoff support depends on your beta setup.

Parallel runs. Separate profiles.

Use separate profiles for separate browser workflows. Ask about remote profile availability for your beta setup.

From first field to final review

Fill multi-page forms with human-like input. Review changes before submitting.

Built for agents.Designed for continuity.

Close the browser. Keep your identity.

One persistent profile

Before restart

Fingerprint saved

After restart

Same fingerprint

MCP

Scoped snapshots. Clear action diffs.

Persistent

Same fingerprint, across restarts.

Fail-closed

Proxy failure stops the run.

How it works

Claude Code

Codex

MCP

Acme Browser

Connect your agent

Link Claude Code or Codex through native MCP.

Choose a profile

Configure your profile identity and proxy controls using the options available in your beta setup.

Run and review

Inspect changes. Step in for verification.

Control, continuity, and isolation

Control

Native MCP: Scoped snapshots and action diffs.
Human-like input: Click, type, scroll.
Human verification: Handoff support varies by beta setup.

Continuity

Persistent fingerprints: A coherent identity across restarts.
Session continuity: Reuse a profile across browser workflows.
Residual risk: Sites can still recognize or challenge activity.

Isolation

Fail-closed proxies: No silent direct fallback.
Separate profiles: Keep each run’s browser state apart.
Remote profiles: Ask about availability in your beta setup.

Questions, answered.

How does Claude Code or Codex control Acme Browser?

Connect through native MCP. The agent inspects scoped page snapshots, takes actions, and reviews what changed through action diffs.

What does “persistent fingerprint” mean?

A profile retains coherent browser characteristics across restarts. Sites can still recognize accounts or correlate other signals.

Is Acme Browser undetectable?

No. Sites can still challenge, restrict, or block activity. Persistent identities and proxy controls do not guarantee invisibility.

What’s the difference between local and remote profiles?

Local profiles run on your machine. Remote profiles run in a separate environment for stronger isolation. Both need an appropriate proxy configuration. Remote profile availability for your beta setup needs confirmation.

What residual risks remain?

IP reputation, account history, behavior, and server-side signals can still identify or correlate activity. Configuration and evolving detection tools also matter.

How are CAPTCHAs and 2FA handled?

CAPTCHA and 2FA can require you to complete verification yourself. Pause, handoff, and resume support depend on the agent and beta setup. Acme does not promise to bypass CAPTCHA or 2FA.

Does it work with other agents besides Claude and Codex?

Other compatible MCP clients may connect. Acme is built for Claude Code and Codex; tool support and handoff vary by client.

How do I get beta access?

Submit your email using either beta form. Your request is saved and invitations are sent manually. Signing up does not provide immediate access or trigger an automated invitation.

Which operating systems are supported, and what does it cost?

Confirm supported operating systems and pricing when arranging your beta invitation. This page does not publish a supported-platform list or a pricing offer.

What happens to the email I submit?

Your email is saved with your signup request so beta invitations can be managed. Invitations are sent manually. Submitting the form does not create a browser account.