Repository navigation
Description
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?
- In the Windows desktop app, open Settings → Computer Use and confirm that Google Chrome is enabled, shows Manage, and has the extension installed.
- Open a new Work chat, type
@, and search for Chrome. In my desktop app,@Chromeis missing from the results. - Select
@Computerand explicitly ask Work to open a public website using your configured local Chrome browser. - Check which browser the permission prompt names. In my test, it said “cloud browser.”
- 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?
@Chromeshould 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
github-actions commentedon Nov 21, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-][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[/+]kimfferreira commentedon Nov 21, 2026
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:
@Chromeis still missing from the Windows desktop app, even though Chrome is enabled under Settings → Computer Use and the ChatGPT browser extension is installed.@Chromestill appears and works on the web and through the extension.@Computerand explicitly requested my local Chrome browser. After approving the prompt, I watched Work open the site in my installed Chrome, in my usual profile.