explaingit

esoyuince/codex-chrome-operator

Analysis updated 2026-05-18

★ 1JavaScriptAudience · developerComplexity · 4/5Setup · hard

TLDR

A local Windows and Chrome automation bridge that lets the Codex AI tool observe and act on web pages under strict, visible policy controls.

Mindmap

mindmap
  root((Codex Chrome Operator))
    What it does
      Lets Codex control Chrome
      Reads and clicks web pages
      Captures screenshots
    Tech stack
      JavaScript
      Node.js daemon
      Chrome extension MCP adapter
    Use cases
      Guided browser automation
      Visible AI-driven actions
      Emergency stop control
    Audience
      Windows developers using Codex
    Setup
      Install native bridge
      Load unpacked extension
      Node.js 24 plus

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let Codex read a page's structure and content before deciding what action to take.

USE CASE 2

Have Codex click, fill, and submit low-risk form actions on an approved site.

USE CASE 3

Capture screenshots of a page for local visual analysis during an automated task.

USE CASE 4

Use the emergency stop command to immediately halt all pending browser actions.

What is it built with?

JavaScriptNode.jsChrome ExtensionMCP

How does it compare?

esoyuince/codex-chrome-operatoracip/slack-claude-agentadii0906/supportiq
Stars111
LanguageJavaScriptJavaScriptJavaScript
Setup difficultyhardmoderatemoderate
Complexity4/53/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Windows-only, requires Node.js 24+, PowerShell, and installing an unpacked Chrome extension plus native messaging host.

In plain English

Codex Chrome Operator is a local automation bridge that lets Codex, an AI coding tool, observe and control a Chrome browser window on a Windows machine. Instead of Codex being limited to code files, this project lets it interact with web pages: reading page content, clicking buttons, filling in forms, and taking screenshots, all while the browser window stays fully visible to the person using it. The system is made of four connected pieces: a Chrome extension, a native messaging bridge, which is a small program that lets Chrome talk to local software, a local operator daemon that acts as the central process enforcing policy, and an MCP adapter that exposes a small set of strict tools to Codex. All communication stays on the local machine, with no remote servers involved in controlling the browser. The key design principle is being conservative by default. A readiness check must pass before anything runs, requiring the daemon to be running, the extension connected, and the target site approved and not blocked by the user. High-impact actions like placing orders, submitting payments, or completing checkout are permanently blocked regardless of instructions, and cannot be unlocked through an approval prompt. An emergency stop command halts all pending actions immediately and blocks new ones until it is cleared. Low-risk actions the tool can perform include clicking, typing, scrolling, selecting options, and pressing keys. It can also read a compact snapshot of the page's structure for faster AI inspection and capture screenshots for local visual analysis. The project targets Windows with Google Chrome, requires Node.js version 24 or newer and PowerShell, and is written in JavaScript. It is aimed at developers who want an AI coding assistant to safely perform guarded, human-visible browser actions rather than run unsupervised background automation.

Copy-paste prompts

Prompt 1
Walk me through installing codex-chrome-operator on Windows and loading the extension.
Prompt 2
Explain how the readiness gate decides whether an origin is safe to automate.
Prompt 3
Show me how to block a specific site from the extension side panel.
Prompt 4
What high-risk actions does this tool permanently refuse to perform?
Prompt 5
Help me run the operator CLI to check status and observe a page.

Frequently asked questions

What is codex-chrome-operator?

A local Windows and Chrome automation bridge that lets the Codex AI tool observe and act on web pages under strict, visible policy controls.

What language is codex-chrome-operator written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, Chrome Extension.

How hard is codex-chrome-operator to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is codex-chrome-operator for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.

Alternatives & similar repos