Skip to main content
Most AI web automation fails in the real world because modern websites are very good at detecting it. Headless browsers leave recognizable fingerprints, robotic mouse movements trigger fraud signals, and missing browser properties get flagged instantly. Miteos solves this with an embedded stealth browser — a real Chromium instance with an authentic fingerprint, human-like behavior, and full session isolation — so your agents can browse any website as if a real person were doing it.
For sites that aggressively detect bots — financial data providers, job boards, e-commerce platforms — the stealth browser significantly improves task success rates compared to standard automation tools.

How the Stealth Browser Works

The stealth browser isn’t a simulated browser or a modified headless instance. It’s a real Chromium process running inside the Desktop app, configured from the ground up to be indistinguishable from a human-operated browser:
  • Authentic browser fingerprint — The browser runs in a visible (non-headless) mode with real plugins, a consistent navigator object, and none of the telltale signatures that bot-detection scripts look for.
  • Randomized environmental properties — User agent strings, screen resolution, timezone, and language settings are randomized per session to prevent cross-session fingerprint correlation.
  • Real GPU and WebGL fingerprints — WebGL renderer and vendor strings reflect the actual GPU on your machine, passing hardware-level fingerprint checks used by sophisticated bot detection.
  • Human-like mouse and scroll behavior — Mouse movements follow Bezier curves to every click target, scrolling uses natural momentum and easing, and all input events are generated through Chromium’s native input pipeline so they are indistinguishable from real user interaction.
  • Per-agent session isolation — Every agent task gets its own isolated browser context with independent cookies, local storage, and fingerprint profile, so one task’s activity never leaks into another’s.

CAPTCHA Handling

When a CAPTCHA appears, the agent detects it automatically and hands control to you rather than attempting to bypass it programmatically:
  1. The agent identifies the CAPTCHA (reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile, Arkose Labs, PerimeterX, and others).
  2. The agent pauses immediately and sends you a notification: “CAPTCHA detected — please solve it.”
  3. The embedded browser is surfaced in the app window so you can interact with it directly and solve the challenge.
  4. Once the CAPTCHA is resolved, the agent detects that it’s gone and resumes the task automatically from where it left off.
You stay in full control without needing to babysit the agent through every page.

Browsing Capabilities

Within the stealth browser, agents can interact with virtually any web content:
  • Navigate to URLs, follow links, and manage browser history
  • Fill forms — text inputs, dropdowns, checkboxes, file uploads
  • Click elements — buttons, tabs, modals, menus, and dynamic UI components
  • Extract data — scrape text, tables, prices, listings, and structured content from any page
  • Take screenshots — capture the visible page state for decision-making or as task deliverables
  • Interact with SPAs and JavaScript-heavy pages — the real browser engine executes all JavaScript, so dynamic content, lazy-loaded elements, and client-side routing all work as expected

Session Isolation

Each agent task runs in a fully isolated browser session. That session has its own:
  • Cookie jar and authentication state
  • Local storage and IndexedDB
  • Browser fingerprint profile
  • Cache and session history
Sessions are automatically destroyed when a task completes. This means agents can run in parallel without interfering with each other, and no session data persists between separate task runs unless you explicitly configure persistent sessions.

Desktop vs. Web Browser

The stealth browser is available whether you use the Desktop app or the Miteos web app — it just runs in a different place:
Desktop AppWeb App
Browser typeEmbedded Chromium inside the Desktop appCloud-hosted stealth browser session
What you seeThe browser is visible inside the app windowA live stream of the remote browser
CAPTCHA handoffYou interact with the embedded browser directlyYou interact via the streamed browser view
BehaviorIdenticalIdentical
From your perspective as the user, both work the same way — you issue tasks, watch the agent browse, and step in when needed. The underlying infrastructure differs, but the experience and results are consistent across both.