App Logo

Give Codex a real browser

Codex writes code well and scrapes badly.
Reduck gives it one call per site, run in your own signed-in Chrome.

Set up Reduck for Codex Talk to us

Set up Reduck now

  1. Create your Reduck account
    Sign in
  2. Install our Chrome extension
    Download from
    Chrome Web Store
  3. Install the latest Codex version
    npm i -g @openai/[email protected]

    The newest release that connects to the Reduck MCP. Later ones can break the handshake, so take this version rather than the @latest tag.

  4. Register the server
    codex mcp add reduck --url https://mcp.reduck.ai

    MCP servers are a paid Codex feature: on a free OpenAI account the server registers but never loads.

  5. Confirm it connected
    /mcp

    Typed inside a Codex session, not in your shell. Reduck and its tools should be listed.

  6. Let scripts run without a prompt each time
    [mcp_servers.reduck] url = "https://mcp.reduck.ai" default_tools_approval_mode = "auto"

    In ~/.codex/config.toml. Without it Codex stops for approval on every single run_script call, which is unworkable for a job that calls twenty. Starting a session with codex --full-auto does the same thing for that session only.

Using Codex Desktop? Open Settings → MCP servers → + Add server, choose Streamable HTTP, name it reduck, point it at https://mcp.reduck.ai, then restart Codex. The version pin and the approval mode above apply there too.

Codex builds a browser every time.
Reduck gives it one to call.

Codex without Reduck
It writes the scraper first Ask Codex for something on a website and it starts a Playwright file, installs a browser, and debugs selectors. The task was the data, not the tool.
The sandbox has no way out Codex runs your code with the network shut, so the fetch it just wrote fails before it sends. The usual fix is to open the sandbox wider than you wanted.
Tomorrow it starts over Whatever it built lives in a temp file and dies with the session. The next window has no memory of it and writes the same thing again.
Codex with Reduck
It calls a script that exists One MCP call names the site and the arguments. Nothing to install, nothing to debug, and the answer comes back in seconds rather than in iterations.
The browser sits outside it The page is loaded by Chrome on your machine, not by code in the sandbox. Codex sees the result, so the sandbox can stay as tight as you like.
It keeps what it built A script is saved to your account under a name. Every later session finds it through the same MCP server, and so does your teammate's.

One MCP server, no packages to install.

01

One command registers the server, and every site in the catalogue becomes reachable. The next site after that costs you no dependency in the sandbox and no line in your config.

02

The Chrome that loads the page is yours, running beside Codex rather than inside it. Your sessions never leave the machine, and the site is served a browser it recognises.

03

What comes back is a typed JSON object, never the HTML. A field the schema promises is a field Codex can branch on without looking at the page.

Two sites, four scripts, one answer

Codex never opens a page. It picks the scripts, calls them, and reads what they return.

Prompt

We ship a changelog tool next quarter. Take the two biggest ones on Product Hunt, read what people said under their launches, then check whether the same complaints show up in their G2 reviews.

Automation
  1. get_product Reads each Product Hunt listing: tagline, makers, topics
  2. get_launch_comments Pulls the comment thread under each launch
  3. get_alternatives Asks G2 which products it ranks against them
  4. get_product_reviews Reads the written reviews, not just the score
Output

One JSON object per product — launch, comments, competitors and reviews — each against the schema its script declares.

What people point it at

Official scripts, already written and already tested.

Close the month without the invoice hunt

Every vendor keeps its invoices behind its own login and its own download button. Codex walks the list, takes the PDFs you are missing, and tells you which vendor still owes you one.

Learn more

Turn post engagement into a shortlist

Say who you want to reach. Codex finds the posts they are reacting to, reads each profile behind a reaction, and hands back only the ones that fit.

Learn more

Buy on Amazon on the evidence

Star ratings hide the thing that will annoy you in a month. Codex opens the listings that matter and reads what recent buyers wrote before it recommends one.

Learn more

Keep up with a topic on X

Name a subject. Codex brings back the posts moving it and the accounts behind them, without an X account, an API key, or your afternoon.

Learn more

Get a doctor's appointment

The hard part is not finding practitioners, it is finding one free when you are. Codex checks the calendars and only shows you the ones with a slot in your window.

Learn more

Run WhatsApp from the terminal

Codex reads the threads you have not answered, drafts a reply with the conversation in front of it, and sends it from your own account. No Business API to apply for.

Learn more
Browse all use cases

Where the automation runs

Your own Chrome for anything that needs your account; ours for everything else.

In your browser Default Run locally with Reduck Chrome extension
In the cloud On demand Run in Reduck cloud browser
Cost & access
Run cost Free up to 100 scripts Free up to ≈ 100 scripts (1h)
Site covers Every authenticated site Auth-based sites coming soon with connectors
Scale & reach
Always-on Needs your device on Independent of your hardware
Parallel runs Limited by your Chrome (usually up to 5) Many sessions in parallel (up to 99)
Geo control Your own location Residential proxies, any country (not antibot bypass)
In your browser Default Run locally with Reduck Chrome extension
Cost & access
Run cost Free up to 100 scripts
Site covers Every authenticated site
Scale & reach
Always-on Needs your device on
Parallel runs Limited by your Chrome (usually up to 5)
Geo control Your own location
In the cloud On demand Run in Reduck cloud browser
Cost & access
Run cost Free up to ≈ 100 scripts (1h)
Site covers Auth-based sites coming soon with connectors
Scale & reach
Always-on Independent of your hardware
Parallel runs Many sessions in parallel (up to 99)
Geo control Residential proxies, any country (not antibot bypass)

Pick your plan

Start free, scale up as you run more.

Starter

Free forever

Discover Reduck: run and build scripts with limited access.

Get started
  • Run up to 100 scripts/month in your browser or in the cloud
  • 1 hour of cloud browser time/month
  • Build unlimited scripts including 3 private ones
  • Community support on Discord
Most popular

Pro

$20 per month

Higher limits and unlimited script building capacity.

Get started
  • Run up to 1000 scripts/month in your browser or in the cloud
  • 10 hours of cloud browser time/month
  • Build unlimited private scripts
  • Project repositories to share scripts with up to 3 people
  • Community support on Discord

Max

$100 per month

Unlimited usage for power users.

Get Max
  • All of Pro, scaled up
  • Run unlimited scripts/month in your browser
  • 50 hours of cloud browser time/month
  • Project repositories with up to 25 people each
  • Priority support

Enterprise

Custom for your org

Scale mission-critical automations across your org.

Talk to us
  • Everything in Max, plus
  • Shared access cookies to third-party apps
  • Central observability, billing, logs & admin panel
  • Unlimited users
  • Dedicated infrastructure: your region or self-hosted, enterprise-grade compliance
  • Premium support with a forward-deployed engineer

FAQ

Codex changed how its CLI talks to remote MCP servers, and releases after 0.141.0 can fail to complete the handshake with Reduck. 0.141.0 is the one we test against. We lift the pin as soon as a later release is clean, so check the setup steps on this page before you upgrade.
Yes. MCP servers are gated behind a Codex Pro subscription; a free OpenAI account accepts the codex mcp add command but never loads the server, so /mcp comes back empty. That is an OpenAI limit, not a Reduck one. Your Reduck account can still be on the free plan.
Codex treats MCP tools as untrusted by default and prompts before each call. Set default_tools_approval_mode = "auto" under [mcp_servers.reduck] in ~/.codex/config.toml to approve the Reduck server once instead of once per call. Scoping it to that one server leaves your approval rules for everything else alone.
No, and that is the point. Codex never loads the page itself, so there is nothing to allow through the sandbox. The MCP call goes out, the browser work happens outside, and a JSON result comes back. You can leave the sandbox on its strictest setting.
It does not carry your credentials. The Chrome extension pairs your own browser to your account, and the script runs there, in the profile where you are already signed in. Codex sends arguments and reads results; the cookies never leave your machine.
Codex Desktop, yes: Settings → MCP servers → + Add server, pick Streamable HTTP, point it at https://mcp.reduck.ai, then restart. ChatGPT on the web can add Reduck as a connector under Settings → Plugins. All of them read the same account and the same scripts.
Tell Codex to write one. The same MCP server carries the authoring tools, so Codex builds the script against the live page, runs it to check the output, and saves it under your handle. From then on it is a call like any other, and a site change can be repaired the same way.

Codex already writes the code, let it drive the browser too

Set up Reduck for Codex