[macOS 27 beta][ChatGPT for Chrome] Gatekeeper repeatedly blocks signed Snowflake minicore dylib

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

ChatGPT Desktop / Codex-integrated build 26.901.22334 (CFBundleVersion 7746)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 27.0.0 arm64 arm macOS 27.0 beta 8, build 26A5425a, Apple Silicon

What issue are you seeing?

The official ChatGPT for Chrome integration repeatedly triggers the following macOS Gatekeeper warning:

“libsf_mini_core_darwin_arm64.dylib” Not Opened
Apple could not verify “libsf_mini_core_darwin_arm64.dylib” is free of malware that may harm your Mac or compromise your privacy.

The available actions are Move to Trash and Done. The warning may appear multiple times. Dismissing it or choosing Move to Trash does not resolve the problem permanently.

The affected library is extracted into a temporary directory similar to:

$TMPDIR/gosnowflake-cgo*/libsf_mini_core_darwin_arm64.dylib

This occurs while the official ChatGPT Chrome native host is running:

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

The Chrome extension details are:

Name: ChatGPT
Version: 1.26.827.12125
Extension ID: hehggadaopoacecdllhhajmbjkdcmajg

Google Chrome version:

152.0.7977.83

The extracted dylib is a valid Mach-O arm64 shared library. Its code signature verifies successfully:

valid on disk
satisfies its Designated Requirement

Signature details:

Identifier=libsf_mini_core_darwin_arm64
Authority=Developer ID Application: Snowflake Computing INC. (W4NT6CRQ7U)
TeamIdentifier=W4NT6CRQ7U
Timestamp=7 May 2026 at 11:35:18

The inspected copy was 35,104 bytes and had this SHA-256 hash:

da320a4cf4ac60295f9ab1c0bf417d798ac96dbf5855ea98e8ca2753c3ae49eb

The file has a com.apple.quarantine attribute whose origin is recorded as Chrome.

Despite the valid Developer ID signature, the macOS Gatekeeper assessment fails. The unified log at 2026-09-04 08:38:31 Europe/Helsinki contains:

Error checking with notarization daemon: 3

This is followed by:

GK evaluateScanResult: 1
team: W4NT6CRQ7U
id: libsf_mini_core_darwin_arm64
bundle_id: NOT_A_BUNDLE
Prompt shown (6, 0), waiting for response

The Gatekeeper UI then reports:

The file “libsf_mini_core_darwin_arm64.dylib” couldn’t be opened.

When Move to Trash is selected, the log can also contain:

Too many levels of symbolic links

and:

The file “libsf_mini_core_darwin_arm64.dylib” doesn’t exist.

These errors reference Gatekeeper's /.nofollow/... representation of the temporary path. The gosnowflake component can subsequently extract another copy into a newly numbered temporary directory, causing the warning to return.

The main ChatGPT application, the current ChatGPT for Chrome native host, and the bundled classic-level.node module all pass their own code-signature verification.

The temporary directory and dylib are owned by the logged-in user and have normal permissions:

Directory: drwx------
File:      -rw-------

The extraction therefore succeeds. This does not appear to be caused by filesystem permissions or insufficient disk space. The rejection happens when macOS evaluates the extracted library.

Screenshot: I will attach a screenshot of the macOS Gatekeeper warning to this issue.

What steps can reproduce the bug?

1. Run macOS 27.0 beta 8 (26A5425a) on an Apple Silicon Mac.
2. Install and launch ChatGPT Desktop build 26.901.22334.
3. Install and enable the official ChatGPT Chrome extension:
   • Version: 1.26.827.12125
   • Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
4. Fully quit and reopen Google Chrome.
5. Open the ChatGPT side panel or start a ChatGPT Work/Codex task that uses Chrome.
6. Wait for the ChatGPT for Chrome native host to start.
7. Observe the Gatekeeper warning for libsf_mini_core_darwin_arm64.dylib.
8. Select Done or Move to Trash.
9. Observe the warning returning, either immediately or after the integration creates another gosnowflake-cgo* temporary directory.

What is the expected behavior?

The official ChatGPT Chrome native integration should start and operate without triggering macOS Gatekeeper warnings.

Any native libraries embedded in or extracted by the integration should be packaged, signed, notarized, and loaded in a way accepted by supported macOS versions.

If macOS 27 beta is not supported, the application should detect that and show a clear compatibility message instead of repeatedly triggering a system malware warning.

Additional information

Troubleshooting already attempted

• Updated ChatGPT Desktop.
• Updated Google Chrome.
• Removed and reinstalled the official Chrome extension several times.
• Signed out of ChatGPT and signed back in.
• Restarted Chrome.
• Restarted ChatGPT Desktop.
• Confirmed that only one ChatGPT desktop application is installed.
• Confirmed that the current Chrome plugin cache and native messaging manifest point to build 26.901.22334.
• Confirmed that the ChatGPT application and native host signatures are valid.

Reinstalling the browser extension does not resolve the issue because the failure appears to involve the local native integration and an extracted Snowflake library rather than the Chrome extension package itself.

Snowflake minicore information

The Snowflake Go driver source confirms that this library is embedded and initialized at runtime:

https://github.com/snowflakedb/gosnowflake/blob/v2.1.0/minicore_provider_darwin_arm64.go

Snowflake added Developer ID signatures to its Windows and macOS minicore binaries in:

https://github.com/snowflakedb/gosnowflake/pull/1790

The dylib inspected on this Mac has that valid Snowflake Developer ID signature. The remaining failure appears to involve notarization, quarantine provenance, or the way the library is extracted and loaded.

Related OpenAI issues

• https://github.com/openai/codex/issues/36349 — macOS 27 beta, ChatGPT for Chrome native host, and a repeated warning for an extracted Python runtime.
• https://github.com/openai/codex/issues/34267 — ChatGPT for Chrome triggers the same “Apple could not verify” warning for another native module.
• https://github.com/openai/codex/issues/28088 — Chrome native host triggers repeated Gatekeeper/SystemPolicy validation.
• https://github.com/openai/codex/issues/42618 — the same ChatGPT Desktop and Chrome extension versions encounter an OS-level native-host denial despite valid signatures.

Assessment

This appears to be a packaging, quarantine-provenance, or notarization issue involving the gosnowflake minicore library extracted by the ChatGPT for Chrome native integration.

Could you please confirm:

1. Whether ChatGPT for Chrome currently supports macOS 27 beta.
2. Which ChatGPT component includes or invokes the gosnowflake driver.
3. Whether the extracted Snowflake minicore dylib is expected to be independently notarized.
4. Whether the library should inherit a Chrome quarantine attribute when extracted.
5. Whether an updated native host or packaging fix is available or planned.

Start by reproducing the warning with the ChatGPT for Chrome native host at ~/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/ChatGPT for Chrome on macOS 27 beta. Read the referenced gosnowflake minicore_provider_darwin_arm64.go and compare related Codex issues 36349, 34267, 28088, and 42618. Done means the supported integration starts without repeated Gatekeeper warnings, or clearly reports that the OS is unsupported.