Unclear whether the Codex Chrome plugin works in Codex CLI
It is unclear whether the official Codex works directly in Codex CLI or only in the desktop Codex app. The appears to point in different directions.
The setup is described under the Codex app flow: add the inside Codex, install the , confirm it is connected, and then start a new Codex thread. The Codex CLI says the CLI can install, list, and remove plugins in general.
The MCP says Codex CLI supports MCP, and MCP can connect tools such as or Playwright. The real question is whether terminal Codex can use the official and extension path, or whether in the CLI is meant to happen through MCP while the official is for the desktop app.
Key points
- The official may not work directly from plain Codex CLI.
- The instructions are written around the desktop Codex app setup flow.
- Codex CLI supports general plugin management, but that does not prove every desktop plugin works the same way.
- Codex CLI can use MCP to connect tools like or Playwright.
- The main issue is separating the official path from MCP-based .