Skip to content

[Windows] @Chrome missing despite being enabled; permission prompt labels local Chrome as cloud browser #62968

Open

Description

@kimfferreira

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

ChatGPT desktop app for Windows: 26.1117.31558

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26300.0 x64

What issue are you seeing?

After updating the ChatGPT desktop app for Windows to version 26.1117.31558, I noticed that @Chrome was no longer available in the @ menu. It previously appeared there and let me select my local Chrome profile.

Under Settings → Computer Use, Google Chrome is enabled, the button shows Manage, and the ChatGPT browser extension is listed as installed. @Computer is available in the Windows desktop app. @Chrome still appears and works when I use ChatGPT in Chrome or through the browser extension.

In a follow-up test in Work on Windows, I selected @Computer and explicitly asked it to use my configured local Chrome browser to open a public website. The permission prompt said it would use the “cloud browser.” After approving it, I watched the task open the website in my installed Chrome browser, in my usual local profile.

What steps can reproduce the bug?

  1. In the Windows desktop app, open Settings → Computer Use and confirm that Google Chrome is enabled, shows Manage, and has the extension installed.
  2. Open a new Work chat, type @, and search for Chrome. In my desktop app, @Chrome is missing from the results.
  3. Select @Computer and explicitly ask Work to open a public website using your configured local Chrome browser.
  4. Check which browser the permission prompt names. In my test, it said “cloud browser.”
  5. After approving the request, observe which browser opens the page. In my test, the page opened in my installed Google Chrome, in my usual profile.

I had already tried new conversations, restarting the app and Windows, and running the app as administrator. @Chrome remained missing.

What is the expected behavior?

  • @Chrome should be selectable in the Windows desktop app when the Chrome integration is enabled and the extension is installed, as described in the browser extension documentation.
  • The permission prompt should accurately identify the browser that will be used.

Additional information

I confirmed that my installed skills are available through the @ menu. The suggested duplicates concern skills missing from the / menu. This report now focuses on the missing @Chrome mention and the browser named in the permission prompt.

Could you confirm whether @Chrome should still be selectable in Windows desktop Work and Codex, and whether there is a supported way to explicitly select the existing local Chrome profile while the mention is unavailable? Could you also clarify why the prompt referred to the cloud browser when Work used my local Chrome profile?

Activity

  1. added
    appIssues related to the Codex desktop app
    on Nov 21, 2026
  2. changed the title [-][Windows] Installed skills missing from / menu and @Chrome unavailable after update[/-] [+][Windows] @Chrome missing despite being enabled; permission prompt labels local Chrome as cloud browser[/+] on Nov 21, 2026
  3. kimfferreira commented on Nov 21, 2026

    @kimfferreira
    Author

    Thanks for flagging the potential duplicates. I reviewed #62715, #62796, #62700, and #62775. All four cover the skills issue from my original report. I confirmed that I can find my installed skills through the @ menu, as explained in #62700.

    I've already updated the title and description of this issue and removed the skills-related material covered by those reports. The issue now focuses on two observations that the suggested duplicates don't cover:

    • @Chrome is still missing from the Windows desktop app, even though Chrome is enabled under Settings → Computer Use and the ChatGPT browser extension is installed. @Chrome still appears and works on the web and through the extension.
    • The permission prompt said “cloud browser” while Work used my local Chrome profile. In a follow-up test in the Windows desktop app, I selected @Computer and explicitly requested my local Chrome browser. After approving the prompt, I watched Work open the site in my installed Chrome, in my usual profile.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-useskillsIssues related to skillswindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions