macOS 26.6.2: Chrome native host fails with `Operation not permitted (os error 1)` despite valid signature

What version of the Codex / ChatGPT App are you using?

ChatGPT Desktop / Codex-integrated build: 26.901.22334

What platform is your computer?

• macOS 26.6.2
• Apple Silicon / arm64

What issue are you seeing?

The ChatGPT/Codex Chrome side panel worked correctly before upgrading macOS to 26.6.2. Immediately after the OS update, the Chrome extension stopped connecting to the native host and shows:

Native transport disconnected

Chrome verbose logs repeatedly show:

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

The Chrome extension itself loads successfully.

Environment

Chrome extension version:

1.26.827.12125

Installed extension ID:

hehggadaopoacecdllhhajmbjkdcmajg

Native messaging manifest:

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.openai.codexextension.json

Native host path from the manifest:

/Users/Sal/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/ChatGPT for Chrome

Diagnostics already completed

The native host exists and is arm64:

Mach-O 64-bit executable arm64

Code signature verification succeeds:

valid on disk
satisfies its Designated Requirement

The binary is signed by:

Developer ID Application: OpenAI OpCo, LLC

The file is not blocked by com.apple.quarantine.

A clean copy of the native host was made outside the plugin cache and extended attributes were removed. The copied binary still immediately returns:

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

This differs from issue #22659, where the binary had an invalid signature. In this case the signature is valid and the failure appears to be an OS-level permission/sandbox regression after upgrading to macOS 26.6.2.

macOS logs

During launch attempts, macOS logs include:

syspolicyd: Process was already in provenance sandbox, skipping

The Chrome log continues to emit:

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

There was also an unrelated Contacts sandbox message from imagent; the native host failure itself remains the repeated EPERM above.

Additional native messaging manifest issue found

The generated com.openai.codexextension.json originally did not include the currently installed Chrome extension ID in allowed_origins.

Installed extension ID:

hehggadaopoacecdllhhajmbjkdcmajg

The manifest contained different IDs. The active extension ID was manually added to allowed_origins, then Chrome and ChatGPT were fully restarted. The connection still failed with the same Operation not permitted (os error 1) error.

This may indicate two separate problems:

1. The native messaging manifest can be generated with stale/incorrect extension IDs.
2. On macOS 26.6.2, the native host is denied a required operation even when its signature is valid.

Steps to reproduce

1. Start from a Mac where the ChatGPT/Codex Chrome integration is working.
2. Upgrade macOS to 26.6.2.
3. Run ChatGPT Desktop build 26.901.22334.
4. Run Chrome with extension 1.26.827.12125.
5. Open the ChatGPT/Codex side panel.
6. Attempt to connect to the desktop app.
7. Observe Native transport disconnected.
8. Launch Chrome with verbose logging and retry.
9. Observe repeated:

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

Expected behavior

The Chrome extension should connect to the native host as it did immediately before the macOS 26.6.2 update.

Actual behavior

The native host fails with EPERM / Operation not permitted, preventing the Chrome extension from connecting.

Regression

Yes. The same Mac, Chrome profile, extension, and ChatGPT installation worked immediately before the macOS 26.6.2 upgrade.

Request

Please investigate macOS 26.6.2 compatibility for the bundled extension-host, especially sandbox/TCC/IPC/socket access, and verify that com.openai.codexextension.json is generated with the correct current Chrome extension ID.

Start by inspecting the generated com.openai.codexextension.json at ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ and the bundled extension-host launch path shown in the report. Reproduce the Chrome native-messaging failure on macOS 26.6.2, then verify that the current extension ID is allowed and that the host no longer fails with EPERM.