Skip to content

Chrome plugin native host fails code signing validation on macOS arm64 #22659

@haoyizhidaxiongmao

Description

@haoyizhidaxiongmao

What version of the Codex App are you using (From “About Codex” dialog)?

26.506.31421 (2620)

What subscription do you have?

ChatGPT PRO5x

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Feedback ID:
df39e725-9f9b-4b8b-b27d-7d393d7c8228

Codex Chrome plugin cannot connect on macOS arm64 because extension-host fails code signing validation.

Environment:

  • macOS, Apple Silicon arm64
  • Codex app version: 26.506.31421 (2620)
  • Chrome plugin: chrome 0.1.7
  • Chrome extension: 1.1.4_0
  • Chrome profile: Default
  • Platform: Darwin 25.5.0 arm64 arm

What happened:
Codex cannot read Chrome tabs through @chrome. Reinstalling the Chrome extension and Codex Chrome plugin, restarting Chrome/Codex, deleting plugin cache, and redownloading the plugin did not fix it.

Diagnostics:
Path:
/Users/chenxijin/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/extension-host

Commands/results:
codesign --verify --verbose=4 .../extension-host
=> invalid signature (code or signature have been modified)
=> In architecture: arm64

.../extension-host --help
=> extension-host: Operation not permitted (os error 1)

Chrome extension installed/enabled and native host manifest is correct, but the native host binary cannot run due to signature validation failure.

What steps can reproduce the bug?

  1. Install/open Codex App on macOS arm64.
  2. Install the Chrome plugin in Codex.
  3. Install and enable the Codex Chrome Extension in Chrome Default profile.
  4. Enable "Allow access to file URLs" for the Chrome extension.
  5. Restart Chrome and Codex.
  6. Ask Codex to use @chrome to read open Chrome tabs.
  7. Codex times out while initializing the Chrome connection and cannot read tabs.
  8. Verify the native host binary manually:

/Users/chenxijin/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/extension-host --help

Actual result:
extension-host: Operation not permitted (os error 1)

Then run:

codesign --verify --verbose=4 /Users/chenxijin/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/extension-host

Actual result:
invalid signature (code or signature have been modified)
In architecture: arm64

What is the expected behavior?

Codex should be able to initialize the Chrome plugin connection and read open Chrome tab metadata through @chrome. The bundled extension-host binary should pass macOS code signing validation and be executable by the native messaging host.

Additional information

Codex in-app feedback was also submitted successfully.

Feedback ID:
df39e725-9f9b-4b8b-b27d-7d393d7c8228

I also tried:

  • Restarting Chrome and Codex
  • Reinstalling the Chrome extension
  • Reinstalling the Codex Chrome plugin
  • Deleting /Users/chenxijin/.codex/plugins/cache/openai-bundled/chrome and reinstalling the plugin
  • Enabling "Allow access to file URLs" for the Chrome extension

The same signature validation error remained after the plugin cache was deleted and redownloaded.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions