AI 产品解读Browser automation agent bridge — connects OpenAI's Codex AI agent to Chrome to perform tasks on websites
Enables AI-driven automation of browser-based workflows (research, form filling, dashboard review, data updates) on websites where the user is already signed in, eliminating manual multi-step browser tasks
User installs the extension alongside the Codex desktop app. The extension connects to the local Codex process via WebSocket. User gives Codex a task, and the AI agent navigates Chrome — opening tabs, clicking elements, filling forms, reading content — in isolated tab groups, asking for user confirmation before sensitive actions.
AI-controlled browser navigation and interaction on any websiteTask-specific tab groups that don't interrupt active browsingForm filling and multi-step workflow automationResearch and context gathering across multiple tabsDashboard and internal tool review with summarizationUser confirmation before sensitive actions (file uploads, site access, history references)
- 目标用户
- OpenAI Codex users / Knowledge workers who use CRMs and internal web apps / Users automating repetitive browser-based research and data entry tasks
- Source code is heavily minified (background.js 144KB, popup JS 201KB) making detailed logic inspection difficult
- No explicit login/auth/account UI code found — may be handled entirely by the native Codex app
- Cannot confirm exact paid tier gating without access to the Codex desktop app source
付费分析未识别到付费功能
The extension itself contains no billing logic, subscription gates, upgrade prompts, or payment UI. The 'upgrade' keyword hit in popup JS and 'license' hit in CSS are from generic library code (React, Tailwind CSS MIT license), not payment features. The underlying OpenAI Codex service may have paid tiers (e.g., ChatGPT Pro), but the extension does not gate features or call billing APIs.
- 置信度
- 75
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 是
- 登录理由
- The extension is a launcher/bridge for OpenAI's Codex agent service. It connects to a local Codex process (CSP allows ws://127.0.0.1:* and nativeMessaging permission). The Codex product requires an OpenAI account. The extension itself has no login UI (no 'login', 'auth', 'account', 'token' keywords found in source), but the underlying Codex service it depends on requires authentication.
It is best in mac.Perfect.
无法稳定链接，垃圾
Unreliable Chrome automation bridge makes the plugin unusable for serious QA I needed this plugin to inspect an already logged-in Chrome session for staging-site QA. Chrome was running, the correct profile opened, the Codex Chrome Extension was installed and enabled, and the native host manifest checked out correctly. Other Codex chats were able to use the same Chrome profile and plugin at the same time. But in this thread, the plugin’s JavaScript/browser bridge crashed before it could do anything useful. Even a minimal bridge test failed before any browser automation code ran, with windows sandbox failed: spawn setup refresh. The plugin could open a blank Chrome window in the right profile, but it could not list existing tabs, claim the logged-in tab, inspect the page, or take screenshots. That makes it unreliable for authenticated QA. Worse, the diagnostics make the extension/profile look healthy while the actual control bridge is broken, leaving the user with no practical recovery path. For a QA workflow, that is a hard failure. This plugin needs better per-thread bridge health checks, clearer failure reporting, a real restart/recovery mechanism, and stronger isolation so one thread does not fail while others work. Until then, I cannot trust it for production or staging QA tasks that require visual confirmation in Chrome.
Chrome plugin on Windows: native messaging registry key missing after reinstalling Codex and Chrome extension "problem": "Windows native host registry key does not exist: HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension"
Conexão irritante no windows, não lançou para linux. Me forçou a usar windows para essa extensão por não ter o codex para linux e a conexão não é boa. Foi umas 3 horas para configurar e depois que precisei usar denovo ja não tava mais funcionando.
perfect
这几天又连接不到Chrome了。还是有Bug
用了一天就用不上了，很烦，然后我就用上Kimi了，也可以实现它一样的功能，如果实在连不上的，你可以去搜索试一下
Errors when Codex tries to connect to it on Windows. node_repl kernel exited unexpectedly "windows sandbox failed: spawn setup refresh"
之前20号还可以用，怎么之后就不行了，真垃圾啊