Use Case
Codex + Ornold
Use Codex to write, adapt, and execute browser automations across antidetect profiles.
Get StartedInstall with one prompt
Open Codex chat, paste this prompt, replace YOUR_TOKEN with your token from mcp.ornold.com, and send. Codex handles the rest.
Why Codex for antidetect browser automation?
Codex pairs code generation with live browser execution. It calls Ornold MCP tools directly — navigation, form filling, CAPTCHA solving — and adapts the flow when pages change.
Key Features
Parallel browser control
Navigate, click, fill forms, and run JS across all connected antidetect profiles simultaneously via MCP tools.Automatic CAPTCHA solving
Detects reCAPTCHA, hCaptcha, Turnstile, and 9 other types. Solves them in parallel across all sessions.Per-profile data
Send unique values (emails, passwords, names) to each browser session in a single batch command.Real-World Use Cases
Profile warm-up
Use short scripts to browse target sites with human-like activity.
Prepare a target URL list per profile
Generate a warm-up script
Run it across all connected browsers
Collect results and retry failures
Structured extraction
Pull data from many profiles without leaning on one identity too hard.
Split URLs across browsers
Run extraction code in parallel
Aggregate outputs from every profile
Handle pagination or CAPTCHA when needed
Frequently asked questions
How does Codex connect to Ornold?Add the Ornold MCP server to your Codex config with `npx ornold-mcp` and your API token. Connect your antidetect browser profiles via CDP. Codex can then call all browser tools directly.
What is Codex best for with Ornold?Codex pairs code generation with live browser execution. It calls Ornold MCP tools directly — navigation, form filling, CAPTCHA solving — and adapts the flow when pages change.
Can Codex run many antidetect profiles in parallel?Yes. Codex handles planning and control, while Ornold executes actions across many connected browser profiles in parallel with shared context and recovery.
