trillhause shared in

Public

Connected Codex plugins to Claude CodePublic

Agent

Claude Code

Model

GLM-5.3

Started

Sep 3, 12:04 AM

Messages79

Downloads0

Workspace

Repo

Trillhouse-Studio/keyflow-infra

Summary

Closed, Completed

Understand
Located installed Codex and plugins.
Understand
Understand
Researched official Codex plugin repository.
Understand
Build
Wired Codex Chrome and computer-use services into Claude Code.
Build

can you find codex computer use and codex chrome plugins? and help me connect claude code to it ?

Codex 0.151.0 is installed locally, and ~/.codex already has computer-use/ and chrome-native-hosts*.json — good sign. Let me dig into the plugin details and your local setup.

🌐 Z.ai Built-in Tool: webReader

Input:

Executing on server...

Output: webReader_result_summary: [{"text": {"title": "Introducing Codex Plugin for Claude Code - Codex - OpenAI Developer Community", "description": "If you already use Claude Code, this Codex plugin is a simple way to bring Codex into the same workflow. \nIt is useful in three cases: a standard Codex review, a more skeptical adver...

Found the key repo — openai/codex-plugin-cc. Let me check its structure for computer-use and Chrome plugins.

🌐 Z.ai Built-in Tool: webReader

Input:

Executing on server...

Output: webReader_result_summary: [{"text": {"title": "GitHub - openai/codex-plugin-cc: Use Codex from Claude Code to review code or delegate tasks.", "description": "Use Codex from Claude Code to review code or delegate tasks. - openai/codex-plugin-cc", "url": "https://github.com/openai/codex-plugin-cc", "content": "Use Codex from ...

Found the official plugin: openai/codex-plugin-cc — delegates to your local Codex CLI (you have codex-cli 0.151.0 already installed). Now let me check if the marketplace ships separate computer-use/Chrome plugins.

This session is being continued from a previous conversation that ran out of context. The summary below covers the earlier portion of the conversation.

Summary:

Primary Request and Intent: The user asked (single message, verbatim): "can you find codex computer use and codex chrome plugins? and help me connect claude code to it ?" Two explicit intents:
- (a) Find/locate the "Codex computer use" and "Codex Chrome" plugins (OpenAI Codex ecosystem components).
- (b) Help connect Claude Code (this CLI) to them — i.e., install/configure the bridge so Claude Code can drive Codex's computer-use and Chrome capabilities.
Key Technical Concepts:
- Claude Code plugins & marketplaces (~/.claude/plugins/installed_plugins.json, known_marketplaces.json, marketplaces/, plugin-catalog-cache.json)
- OpenAI "Codex Plugin for Claude Code" (community post: delegates through local Codex CLI and Codex app server, reusing local auth, config, environment, and MCP setup)
- Codex computer-use (local component; ~/.codex/computer-use/ directory exists)
- Codex Chrome extension + native messaging hosts (~/.codex/chrome-native-hosts.json, chrome-native-hosts-v2.json, ~/.codex/browser/)
- Codex CLI 0.151.0 at /Users/millin/.local/bin/codex, config at ~/.codex/config.toml, auth at ~/.codex/auth.json
- Claude in Chrome (Anthropic's competing extension, docs: https://code.claude.com/docs/en/chrome)
- Repo context: branch codex/worklayer-mac-local-runtime, latest commit "feat(worklayer-mac): prove local Codex MCP runtime" — user has already proven a local Codex MCP runtime in this repo
- context-mode MANDATORY routing rules from CLAUDE.md: curl/wget BLOCKED in Bash, WebFetch BLOCKED, inline HTTP in Bash BLOCKED — use ctx_* MCP tools / WebSearch instead; Bash only for short-output commands; responses <500 words, ASD-STE100, terse; artifacts written to files, never inlined
- Caution: ~/.codex/auth.json exists — never dump credentials/secrets into context
Files and Code Sections:
- ~/.claude/plugins/ (listed, not read)
  - Contains: blocklist.json, cache, data, installed_plugins.json, known_marketplaces.json, marketplaces, plugin-catalog-cache.json
  - Important: installed_plugins.json and known_marketplaces.json are the next files to inspect to see current plugin state and how to add the Codex plugin/marketplace.
- ~/.codex/ (listed, not read)
  - Contains (head -20): agents, AGENTS.md, ambient-suggestions, archived_sessions, attachments, auth.json, automations, browser, cache, chrome-native-hosts-v2.json, chrome-native-hosts.json, computer-use, config.toml, cross-instance-locks, dictation-history, generated_images, goals_1.sqlite (+shm/-wal), herdr-agent-state.sh
  - Important: confirms Codex computer-use (computer-use/), Codex Chrome native hosts (chrome-native-hosts*.json), and browser/ are already installed locally. config.toml will show how Codex exposes MCP/app-server. Do not print auth.json contents.
- No files were created or modified yet — research phase only.
Errors and fixes:
- No errors so far. Both tool calls (WebSearch + Bash listing) succeeded on first attempt.
- Note: context-mode rules blocked WebFetch/curl; I correctly used the native WebSearch tool and plain ls/which Bash (short output) instead.
Problem Solving:
- Verified local environment state: Codex CLI 0.151.0 installed; Codex computer-use and Chrome native-host components present under ~/.codex; Claude Code plugin infrastructure present under ~/.claude/plugins.
- Identified the most promising bridge: the official "Codex Plugin for Claude Code" (OpenAI Community post at https://community.openai.com/t/introducing-codex-plugin-for-claude-code/1378186) which delegates through the local Codex CLI/app server — matching the user's existing local Codex runtime work on this branch.
- Not yet done: reading the community post for exact install steps; inspecting installed_plugins.json / known_marketplaces.json; checking ~/.codex/computer-use and ~/.codex/browser contents; actually installing/connecting.
All user messages:
- "can you find codex computer use and codex chrome plugins? and help me connect claude code to it ?" (No other user turns; no corrections or feedback given yet.)
Pending Tasks:
- Determine exact nature of "Codex computer use" and "Codex Chrome" plugins (local Codex components vs. Claude Code plugin marketplace packages) — partially done, needs confirmation of install mechanism.
- Fetch the OpenAI Community post "Introducing Codex Plugin for Claude Code" for installation instructions (use ctx_fetch_and_index or mcp__web_reader__webReader, NOT WebFetch/curl).
- Inspect ~/.claude/plugins/installed_plugins.json and known_marketplaces.json for current state; inspect ~/.codex/config.toml, ~/.codex/computer-use/, ~/.codex/browser/ for how Codex exposes these capabilities (avoid auth.json secrets).
- Install/connect: likely claude plugin marketplace add ... + claude plugin install ... or MCP config, then verify connection (e.g., list tools).
- Reply to user with findings + sources as markdown links (WebSearch reminder requires citing: community.openai.com post, code.claude.com/docs/en/chrome, thenewstack.io article).
Current Work: Immediately before this summary, I had just received results from the first parallel research batch (WebSearch + local environment inspection) responding to the user's request to find Codex computer-use and Codex Chrome plugins and connect Claude Code to them. Key established facts: Codex CLI 0.151.0 installed at /Users/millin/.local/bin/codex; ~/.codex/ contains computer-use/, browser/, chrome-native-hosts.json, chrome-native-hosts-v2.json; ~/.claude/plugins/ has standard plugin infrastructure (installed_plugins.json, known_marketplaces.json, marketplaces/); web search surfaced the official "Codex Plugin for Claude Code" as the bridge. No response has been sent to the user yet, and no connection steps have been performed.
Optional Next Step: Continue the user's request ("help me connect claude code to it"): fetch the OpenAI Community post "Introducing Codex Plugin for Claude Code" (https://community.openai.com/t/introducing-codex-plugin-for-claude-code/1378186) via ctx_fetch_and_index or mcp__web_reader__webReader to get exact install commands, and in parallel inspect ~/.claude/plugins/installed_plugins.json, ~/.claude/plugins/known_marketplaces.json, ~/.codex/config.toml (small reads or ctx tools) to see current wiring. Then execute the install (e.g., claude plugin CLI or MCP config) and verify Claude Code can reach the Codex computer-use/Chrome tools, reporting back tersely with source links.

If you need specific details from before compaction (like exact code snippets, error messages, or content you generated), read the full transcript at: /Users/millin/.claude/projects/-Users-millin-Documents-Code-keyflow-infra/7b338dda-af50-47ed-8584-83382d4c8c76.jsonl Continue the conversation from where it left off without asking the user any further questions. Resume directly — do not acknowledge the summary, do not recap what was happening, do not preface with "I'll continue" or similar. Pick up the last task as if the break never happened.

Found what exists. Before connecting, let me check your local Codex wiring and the claude CLI.

Your Codex install already has both capabilities as MCP servers — this is the key finding:

Codex Computer Use: ~/.codex/computer-use/Codex Computer Use.app → SkyComputerUseClient (MCP server computer-use, currently disabled; cua_repl/node_repl unified plugin enabled)
Codex Chrome: native messaging hosts (chrome-native-hosts-v2.json) + browser plugin at ~/.codex/plugins/cache/openai-bundled/browser/ with BROWSER_USE_AVAILABLE_BACKENDS = "chrome,iab"

There is no standalone "Codex computer-use/Chrome" plugin for Claude Code — the official openai/codex-plugin-cc marketplace ships one codex plugin that delegates through your local Codex CLI + app server, reusing its MCP setup (issue #446 requests a direct /codex:computer-use — not shipped yet). Two connection paths: install the official plugin, and wire the computer-use MCP server directly. Doing both now.

The classifier blocked the claude plugin CLI call. Let me try the direct MCP route.

Request interrupted by user

continue

Computer-use MCP added to user config. Verifying it launches and responds:

Connected. Now probing what tools it exposes (desktop only, or browser too), and grabbing the Codex browser plugin env from config:

Desktop tools confirmed (list_apps, get_app_state, click…). Now probing the Codex Chrome/browser service (node_repl with the chrome+iab backends):

Done. Here's the full picture:

What "Codex computer use" and "Codex Chrome" actually are

Not Claude Code plugins — they're local Codex components on your machine:

Computer Use: ~/.codex/computer-use/Codex Computer Use.app (SkyComputerUseClient)
Chrome: extension native hosts (~/.codex/chrome-native-hosts-v2.json) + browser plugin with chrome,iab backends

The only official Claude Code bridge is openai/codex-plugin-cc — one plugin that delegates to your local Codex CLI/app server. It has no computer-use/Chrome commands yet (issue #446 requests it).

Connected ✅

Codex Computer Use → Claude Code (direct MCP, user scope):

Added codex-computer-use to ~/.claude.json, health check ✔ Connected
Verified tools: list_apps, get_app_state (screenshot + accessibility tree), click, …
Restart Claude Code to load the tools — they appear as mcp__codex-computer-use__*

Chrome — two routes, your pick

Install the official Codex plugin (my install call was blocked by the permission classifier — run these yourself):
```
! claude plugin marketplace add openai/codex-plugin-cc! claude plugin install codex@openai-codex
```
Then restart and run /codex:setup. Chrome work goes through delegation (/codex:rescue …) — Codex uses its own Chrome extension. Uses your existing Codex login/config (announcement).
You already have chrome-devtools-mcp installed in Claude Code — native Chrome control without Codex.

I did not wire Codex's node_repl/cua_repl into Claude Code: it's a raw JS REPL service, not clean browser tools — wrong shape, and redundant with option 1 or 2.

Sources: codex-plugin-cc · OpenAI announcement · issue #446

still do it, I like how codex uses chrome. I will disable chrome-devtools-mcp

Good call — let me wire the actual Codex Chrome path (cua_repl unified service) into Claude Code. First I need its real env values (they were redacted in codex mcp list):

The plugin's .mcp.json has the full env — cua_repl wraps the same REPL but steered at Chrome/browser control (CUA_REPL_ENABLED_SURFACES=browser,computer, chrome backend preferred). Probing it standalone before wiring:

The cua_repl service runs standalone and exposes the real Codex Chrome API (cua.getState(), cua.getTab(), cua.createBrowserTab()…). Wiring it in as codex-browser:

Done — both Codex surfaces are now wired into Claude Code:

MCP server	What it gives	Status
`codex-computer-use`	macOS desktop control (`list_apps`, `get_app_state`, `click`…)	✔ Connected
`codex-browser`	The real Codex Chrome path — `cua` API (`cua.getState()`, `cua.getTab()`, `cua.createBrowserTab()`), chrome backend preferred, in-app browser as fallback	✔ Connected

codex-browser is the exact same cua_repl service Codex runs (env copied verbatim from the plugin's .mcp.json), registered at user scope in ~/.claude.json.

To use: restart Claude Code. Tools appear as mcp__codex-browser__js / __js_reset — the js tool ships with Codex's full CUA instructions, so "open example.com in Chrome and log in" just works the way it does in Codex.

Two caveats:

The config pins plugin version 26.831.21537 — when the ChatGPT app updates its bundled plugins, the path breaks. Fix = re-add with the new version dir. Tell me and I'll re-run it.
Chrome control flows through the extension's native messaging host — if the Codex/ChatGPT app is actively using Chrome at the same moment, they may contend for the connection.

Go ahead and disable chrome-devtools-mcp whenever — these don't depend on it.

What "Codex computer use" and "Codex Chrome" actually are

Not Claude Code plugins — they're local Codex components on your machine:

Computer Use: ~/.codex/computer-use/Codex Computer Use.app (SkyComputerUseClient)

Chrome: extension native hosts (~/.codex/chrome-native-hosts-v2.json) + browser plugin with chrome,iab backends

The only official Claude Code bridge is openai/codex-plugin-cc — one plugin that delegates to your local Codex CLI/app server. It has no computer-use/Chrome commands yet (issue #446 requests it).

Connected ✅

Codex Computer Use → Claude Code (direct MCP, user scope):

Added codex-computer-use to ~/.claude.json, health check ✔ Connected

Verified tools: list_apps, get_app_state (screenshot + accessibility tree), click, …

Restart Claude Code to load the tools — they appear as mcp__codex-computer-use__*

Chrome — two routes, your pick

Install the official Codex plugin (my install call was blocked by the permission classifier — run these yourself): Then restart and run /codex:setup. Chrome work goes through delegation (/codex:rescue …) — Codex uses its own Chrome extension. Uses your existing Codex login/config (announcement).

You already have chrome-devtools-mcp installed in Claude Code — native Chrome control without Codex.

I did not wire Codex's node_repl/cua_repl into Claude Code: it's a raw JS REPL service, not clean browser tools — wrong shape, and redundant with option 1 or 2.