macOS 26.825.41651: Brave/Chrome shown installed but native-host manifests and chrome/latest are missing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
On macOS, ChatGPT Desktop reports the Brave Browser extension as installed and enabled, but the Brave side panel says "Install the app to use ChatGPT in Brave." The desktop app is installed and running.
The bundled external-browser plugin is installed and current, and its signed native-host executable exists in the versioned plugin directory. However, the install/repair flow creates neither the chrome/latest indirection nor the Native Messaging manifest for Brave or Chrome.
This reproduces on a newer build than the related reports #38530 and #37059.
Environment
- ChatGPT Desktop:
26.825.41651(build7345) - Embedded Codex CLI:
0.151.0-alpha.7.1 - macOS:
26.5, Apple Silicon (arm64) - Brave Browser:
151.1.93.138 - ChatGPT browser extension:
1.2.27268.51612_0 browser@openai-bundled: installed and enabled,26.825.41651chrome@openai-bundled: installed and enabled,26.825.41651
Actual behavior
- Brave is running.
- The extension is installed and enabled in the selected Brave profile.
- ChatGPT Settings -> Computer use shows Brave as installed and enabled.
- The Brave extension side panel says the desktop app must be installed.
- The expected Brave manifest is absent:
<home>/Library/Application Support/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.openai.codexextension.json
exists: false
correct: false
- The expected Chrome manifest is also absent, so this is not limited to Brave:
<home>/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.openai.codexextension.json
exists: false
correct: false
- The current versioned native-host executable does exist:
<home>/.codex/plugins/cache/openai-bundled/chrome/26.825.41651/extension-host/macos/arm64/ChatGPT for Chrome
- The cache root contains the versioned directory but no
chrome/latestentry.
Supported recovery attempts
- Toggled Brave integration off and on in ChatGPT Settings.
- Removed and reinstalled the Brave extension through ChatGPT Settings.
- Removed and reinstalled
browser@openai-bundledwith the officialcodex pluginmanager. - Installed
chrome@openai-bundledwith the official plugin manager. - Restarted the internal app service.
- Fully quit and reopened ChatGPT Desktop.
- Rechecked Brave and Chrome with the bundled diagnostic scripts.
The UI continued to report success, but the manifests and chrome/latest remained absent.
Expected behavior
Installing or repairing an external browser integration should atomically:
- install and enable the current bundled Chrome/external-browser plugin;
- create or update
chrome/latestto the active version; - create the Native Messaging manifest for every enabled supported Chromium browser, including Brave;
- verify that the manifest target exists and is executable before showing an installed/healthy state.
Privacy
All account identifiers, usernames, private project paths, browser history, logs, tokens, and screenshots have been omitted. Paths above use <home> intentionally.
Related
- #38530
- #37059
- #31904
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the bundled plugin install or repair flow and checking the reported ~/.codex/plugins/cache/openai-bundled/chrome/26.825.41651 path, chrome/latest entry, and browser NativeMessagingHosts manifests. Trace the diagnostic scripts and plugin-manager entry points mentioned in the issue; done means enabled Brave and Chrome integrations create valid manifests targeting an existing executable and report healthy only after verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- cli, desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100