openai / openai/codex

[Windows] Chrome and Edge extensions cannot detect ChatGPT desktop app due to stale native host path

Open
#42,582 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Environment
  • Windows x64
  • ChatGPT desktop app: 26.901.20858
  • CODEX_HOME: E:\GPT\xiaozhi-ai-root\runtime\CodexData
  • Chrome extension: 1.26.827.12125_0
  • Edge extension: 1.26.901.11451_0
Problem

Both Chrome and Edge extensions cannot connect to the ChatGPT desktop app. The browser side panel continues to display:

"Install the app to use ChatGPT in Chrome"

The ChatGPT desktop app is already installed and running.

Root cause found

The shared native messaging manifest is located at:

C:\Users\Administrator\AppData\Local\OpenAI\extension\com.openai.codexextension.json

It still points to this missing executable:

C:\Users\Administrator.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exe

That file does not exist.

The current valid native host exists at:

E:\GPT\xiaozhi-ai-root\runtime\CodexData\plugins\cache\openai-bundled\chrome\26.901.20858\extension-host\windows\x64\extension-host.exe

No extension-host process starts. Both Chrome and Edge fail because they share this native messaging host.

Steps already tried
  • Repaired the ChatGPT Windows app
  • Completely uninstalled and reinstalled the ChatGPT desktop app
  • Reinstalled the Chrome extension
  • Installed and tested the Edge extension
  • Restarted ChatGPT, Chrome, and Edge
  • Started a new Codex chat
  • Opened the ChatGPT browser side panel
  • Used "open the app if already installed"

The problem remains after all steps.

Expected behavior

Reinstalling ChatGPT or the browser integration should rewrite the native messaging host path to the active CODEX_HOME location.

Feedback ID

01a067b0-b562-7fd1-b665-150a8b8d5ae8

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.

Research direction

Start by inspecting the shared native messaging manifest at C:\Users\Administrator\AppData\Local\OpenAI\extension\com.openai.codexextension.json and compare its executable path with the active CODEX_HOME path reported in the issue. Trace the Windows desktop-app or browser-integration setup responsible for that manifest, then verify that reinstalling rewrites the path and allows Chrome and Edge to connect.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.