ChatGPT Chrome Extension Not Seeing Your Tabs? 7 Checks
Short answer: Tab reading and tab control in the ChatGPT Chrome extension run through the ChatGPT desktop app, not the website. You @-mention the browser inside a Work or Codex chat, and the extension only works in the browser profile where it was installed. If @Chrome is missing or the tab list is empty, OpenAI’s documentation gives seven checks in order: update the app, restart the browser, confirm the browser shows Manage under Computer Use, switch to the right profile, start a new chat, restart the app, then reinstall from the Computer Use screen. Most cases end at check three.
OpenAI announced on October 15, 2026 that its ChatGPT extension for Chrome can now look across your open tabs, answer questions about them, and in Work mode take over tabs to fill forms, send messages, download files, and group tabs. The Chrome Web Store listing was refreshed the next day and shows about 7,000,000 users.
The announcement made it sound like you install the extension and ChatGPT just sees everything. It does not work that way, and that gap is why the tab feature looks broken for a lot of people on day two.
Based on OpenAI’s browser-extension documentation, the Chrome Web Store listing (version 1.26.1005.11759), and the October 15 announcement coverage, all read on October 17, 2026. Plan requirements are stated by OpenAI only where noted.
What This Covers
- What changed in the ChatGPT Chrome extension on October 15, 2026?
- Why can’t ChatGPT see my open tabs?
- The 7 Checks, in OpenAI’s Order
- Does tab control need a paid ChatGPT plan?
- Which permission should you pick at the prompt?
- Does it work in Edge, Brave, Opera, or Vivaldi?
- Keeping Banking and Work Tabs Out of Reach
- Tips
- Warnings
- FAQ
- Sources
What changed in the ChatGPT Chrome extension on October 15, 2026?
The ChatGPT Chrome extension gained two tab-related modes on October 15, 2026: Chat, where ChatGPT reads across your open tabs to answer a question, and Work, where ChatGPT controls those tabs to complete a task. OpenAI described it on its ChatGPT account as bringing computer use to anyone who uses Chrome.
In practice the split matters more than the headline.
- Chat: you tag the browser and ask something like “compare the prices on my three open product tabs.” ChatGPT reads, it does not click.
- Work: ChatGPT opens, fills, downloads, and groups. It asks before touching each new site unless you have already allowed that site.
When I compared the coverage from The Decoder, Unite.AI, and PiunikaWeb against OpenAI’s own extension documentation, the documentation was the only source that explained where the feature actually lives. The extension itself has had tab mentions since the August 31, 2026 expansion to more browsers. What is new is the depth of the Work actions and the wider rollout.
Why can’t ChatGPT see my open tabs?
The ChatGPT extension exposes your open tabs to the ChatGPT desktop app, so a ChatGPT tab on chatgpt.com in the same browser will not list them. According to OpenAI’s browser-extension docs, you start a ChatGPT Work or Codex chat in the desktop app, open the @ menu, and select your browser, for example “@Chrome open the pricing tab and summarize it.”
Three things have to be true at the same time:
- The ChatGPT desktop app is installed and signed in to the same account as the extension.
- Settings > Computer Use in the desktop app shows your browser with a Manage button, not Install.
- You are using the browser profile where the extension was installed. A second Chrome profile, even on the same machine, is invisible.
This part trips a lot of people up. The side panel you open from the toolbar is side chat. It can read the page you are on, take highlighted text, and sync with the app. It is not the same thing as the app-side tab mention, and on Opera side chat is not available at all.
I noticed that the Chrome permission screen does not mention the desktop app anywhere, so it is easy to install the extension, grant everything, and still have nothing to @-mention because the app half was never set up.
The 7 Checks, in OpenAI’s Order
OpenAI’s extension documentation lists these troubleshooting steps, and the order is deliberate: the cheap checks come first.
| # | Check | What it rules out |
|---|---|---|
| 1 | Update the ChatGPT desktop app. Remove extra copies of the extension if you installed more than one. | Old app build that predates the October 15 feature set |
| 2 | Restart the browser and confirm side chat loads from the toolbar (skip on Opera). | Extension not actually running |
| 3 | Open Settings > Computer Use in the app. The browser must show Manage. If it shows Install, run setup again. | App and extension never paired |
| 4 | Switch to the browser profile where the extension is enabled. | Wrong profile, the most common cause on shared machines |
| 5 | Start a new Work or Codex chat and @-mention the browser again. | Stale chat that was opened before pairing |
| 6 | Restart the desktop app. | Background helper stuck |
| 7 | Reinstall the extension through Settings > Computer Use, then run /feedback in the app and send the chat ID to support if it still fails. | Corrupted install |
Before any of that, OpenAI’s docs say to confirm the site you are asking about is not on your blocklist. A blocked domain simply will not appear, with no error.
One more case from OpenAI’s developer forum: the extension could read pages but would not click or type, and the native host looked healthy. It recovered after restarting both the browser and the app, which is checks 2 and 6. That is a single report, not an official fix, but it matches the documented order.
Does tab control need a paid ChatGPT plan?
OpenAI’s browser-extension documentation does not state a plan requirement for tab mentions or browser control, and Unite.AI’s October 15 report said the updated extension is available on all ChatGPT plans. PiunikaWeb reported the opposite for Work mode, saying it needs at least Plus.
So the honest answer is: the reading side is documented as plan-free, the acting side is disputed. If you are on Free and the Work option is simply absent from your app, treat that as a plan gate rather than a bug and do not spend an hour on the seven checks. If you are on Plus or higher and Work is there but the browser is not in the @ menu, it is a setup problem and the checks apply.
Honestly, that is usually enough to sort out which camp you are in.
Which permission should you pick at the prompt?
By default, ChatGPT asks before interacting with each new website, keyed on the host such as example.com, and OpenAI’s documentation offers four responses at that prompt.
| Option | What it does | Risk label in OpenAI’s docs | When it makes sense |
|---|---|---|---|
| Allow once | Permission for this request only | None | First time on any site |
| Allow for this site | Remembers the host | None | A site you automate weekly, with no money or private data on it |
| Allow for all sites | Skips the prompt everywhere | Elevated Risk | Almost never for a personal profile |
| Decline | Refuses, task stops or reroutes | None | Any site you did not expect ChatGPT to touch |
Browser history is handled separately. ChatGPT asks each time it wants to read history, the request is labeled Elevated Risk, and there is no always-allow option. Downloads and uploads also prompt by default.
The install-time Chrome prompt is broader than the runtime prompts. The extension asks to read and change data on all websites, read browsing history across signed-in devices, manage downloads, read bookmarks, display notifications, manage tab groups, access the page debugger, and talk to native applications. OpenAI’s explanation is that these are what it takes to operate a browser, and that its own confirmations, allowlists, and blocklists sit on top of them.
You will probably notice that the Chrome prompt and the ChatGPT prompt disagree about how much access you are giving. Chrome is describing the ceiling. ChatGPT’s per-site prompt is where you actually set the floor.
Does it work in Edge, Brave, Opera, or Vivaldi?
OpenAI’s extension documentation lists five supported browsers as of October 2026, and all five support tab mentions and browser control from the desktop app, while side chat is missing only on Opera.
| Browser | Tab mentions and control | Side chat panel |
|---|---|---|
| Chrome | Yes | Yes |
| Edge | Yes | Yes |
| Brave | Yes | Yes |
| Vivaldi | Yes | Yes |
| Opera | Yes | No |
Two details from the docs matter for troubleshooting. First, if your browser is not listed under Computer Use, expand More browsers before assuming it is unsupported. Second, the @-mention uses the browser’s name, so in Edge it is @Edge, not @Chrome. People search for “@chrome not showing” when they are on Brave and the command was never going to be @Chrome.
If you want ChatGPT to use its own sandboxed browser instead of your tabs, the mention is @Browser. That built-in browser does not see your Chrome profile, cookies, or extensions, which is the point of it.
Keeping Banking and Work Tabs Out of Reach
Chat mode reads across whatever tabs are open in the paired profile. The practical defense is to decide which profile ChatGPT lives in, not to hope it ignores the wrong tab.
- Install the extension in a secondary Chrome profile used for research and shopping. Keep banking, email, and admin consoles in your main profile, which the extension cannot see.
- Add your bank, brokerage, and health portals to the blocklist in Computer Use. Blocklists and allowlists are shared across all supported browsers, so you set them once.
- Never answer the first prompt with Allow for all sites. Allow once costs you one click per task and keeps the Elevated Risk option off.
- Close signed-in work tabs before a Work task. The extension can act on sites where you are already logged in, which is useful for Salesforce and dangerous for a payroll portal.
OpenAI says it stores browser activity only when it becomes part of the ChatGPT context, and that Computer Use follows your Memories setting. If you have memory on, a tab you let ChatGPT read can end up referenced in a later chat.
If you are also deciding whether to connect ChatGPT to Slack, email, or Drive, the permission trade-offs are similar and we covered them in Before You Connect a ChatGPT Dot to Slack, Email, or Drive. And if Chrome itself is already struggling, a heavy extension on top will not help; our guide to Chrome using too much memory on Windows is the place to start.
Tips
- Name tabs clearly before a Work task. ChatGPT groups and targets tabs by what it can read, and five tabs titled “Dashboard” are a coin toss.
- Open the Manage screen once a month and revoke sites you no longer automate. Allow-for-this-site grants do not expire on their own.
- For file uploads from Chrome, turn on “Allow access to file URLs” in the extension’s Details page, then restart the task. OpenAI documents this as a separate switch.
- On macOS, Cmd+Shift+. opens side chat without touching the toolbar.
Warnings
- Check the publisher before installing. The Chrome Web Store has many “ChatGPT” sidebars from other developers, and only the one offered by OpenAI pairs with the desktop app.
- Allow for all sites is labeled Elevated Risk by OpenAI for a reason. It removes the only per-site gate you have.
- A tab that is on your blocklist will not error, it will just be absent. If a site never shows up, check the blocklist before reinstalling anything.
- Do not run a Work task with a payment page open in the same profile unless you intend ChatGPT to be able to act on it.
FAQ
Can the ChatGPT website read my Chrome tabs without the desktop app?
No. OpenAI’s documentation routes tab mentions and browser control through the ChatGPT desktop app’s Work or Codex chats. The browser-side panel is side chat, which reads the current page and highlighted text but does not expose your tab list.
Why does @Chrome work on my laptop but not my desktop with the same account?
The extension pairs per machine and per browser profile. Each computer needs the desktop app installed, Computer Use showing Manage for that browser, and the same profile where the extension was enabled. Signing in to the same ChatGPT account does not carry the pairing across machines.
Does the ChatGPT extension read my tabs in the background all the time?
OpenAI says the extension works in the background without taking over your active browsing session, and that it asks before using each new website. It stores browser activity only when that activity becomes part of a ChatGPT conversation, so tabs you never mention in a chat are not part of the context.
Sources
- OpenAI — Browser extension documentation (setup, supported browsers, permissions, troubleshooting)
- Chrome Web Store — ChatGPT extension by OpenAI (version 1.26.1005.11759, listing updated October 16, 2026)
- OpenAI Help Center — Using the built-in browser in the ChatGPT desktop app (@Browser vs. your own Chrome profile)
- Unite.AI — OpenAI Brings Computer Use to Chrome With ChatGPT Tab Controls (October 15, 2026)
- The Decoder — ChatGPT becomes a full Chrome browser assistant (October 16, 2026)
- OpenAI Developer Community — Chrome control became read-only, recovered after a clean restart
🔗 Related guides
Fact-checked against OpenAI’s browser-extension documentation, the Chrome Web Store listing, and the October 15–16, 2026 announcement coverage as of October 17, 2026. Plan availability for Work mode was reported differently by two outlets and is flagged as unconfirmed above. This is not official OpenAI guidance.
