[macOS 27 beta] ChatGPT for Chrome native host triggers repeated Python.framework alert

Open
#36,349 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos, python
Domain
desktop, operating-systems, security

Research direction

No repository file or test is named. Start by tracing the bundled ChatGPT for Chrome native host launch and the extracted Python 3.12 runtime, using the reported AMFI security logs as the first diagnostic reference; done means the host starts on macOS 27 beta without the repeated Python.framework alert.

Written by the indexing model from the issue text.

Description

app browser bug

Summary

On macOS 27 beta, the bundled ChatGPT for Chrome native host triggers a repeated macOS alert stating that Python.framework is damaged and should be moved to the Trash.

This does not appear to involve a separately installed system Python: reinstalling Python 3.14 does not change the behavior. The native host instead extracts and attempts to run its bundled Python 3.12 runtime.

Environment

  • macOS 27 beta, Apple Silicon
  • ChatGPT macOS: 26.727.40816
  • Google Chrome: 150.0.7871.187
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg

Steps to reproduce

  1. Install and enable the bundled ChatGPT for Chrome extension from ChatGPT desktop.
  2. Quit and reopen Google Chrome.
  3. Click the ChatGPT for Chrome extension icon to activate it.
  4. Dismiss the macOS alert and retry.

Actual behavior

A macOS alert repeatedly reports that Python.framework is damaged. The alert returns after dismissing it or choosing Move to Trash.

System security logs show the native host extracting a temporary PyInstaller-style runtime and AMFI rejecting its embedded Python:

$TMPDIR/_MEI.../Python.framework/Versions/3.12/Python
AMFI: ... is adhoc signed
amfid: ... not valid: The file is adhoc signed or signed by an unknown certificate chain

The Chrome native host process is launched from the bundled Chrome plugin cache as ChatGPT for Chrome; this is not a third-party ChatGPT extension.

Expected behavior

The bundled Chrome native host should start without a Python.framework security alert.

Notes

  • Reinstalling Python 3.14 succeeded but did not affect this issue, because the failing runtime is the native host's bundled Python 3.12.
  • The issue reproduces after restarting Chrome and activating the extension.
  • I have intentionally omitted user-specific paths, account details, session identifiers, and local logs.

Could you confirm whether the native host is supported on macOS 27 beta and whether an updated host packaging/signing fix is available?

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.