<![CDATA[Opera Browser Connector for ChatGPT repeatedly disconnects during active use]]>Hello,

I am reporting a persistent reliability problem with the Opera Browser Connector used with ChatGPT on Windows.

Environment:

  • Windows 10 Pro
  • Opera desktop browser
  • One Opera profile
  • Signed in to Opera
  • “Allow AI connection” enabled
  • ChatGPT used actively together with Opera

Problem:
The Browser Connector repeatedly disconnects during active use, not only after being idle.

The recurring error is:

UNAVAILABLE: Error code: UNAVAILABLE; Error: McpServerError: Browser not connected. Make sure to enable "Allow AI connection" in the "Browser Connector" and sign in with your Opera account.

This happens even when:

  • Opera is open
  • I am signed in
  • the connector has just been working successfully
  • I am actively using the browser
  • “Allow AI connection” is already enabled

Typical workflow:

  1. ChatGPT successfully reads open Opera tabs.
  2. It successfully reads page content or takes a screenshot.
  3. On the next action, the connector suddenly returns “Browser not connected”.
  4. The connection has to be manually restored.
  5. The same problem repeats again shortly afterwards.

Real examples from my current work:

  • Cloudflare DNS management
  • Netlify domain configuration
  • Opera forums itself

The connector has disconnected multiple times during the same active session while moving between these pages.

This makes the connector unreliable for any serious workflow because a multi-step task cannot be completed consistently.

Please investigate:

  1. Why the connector loses the session while Opera is still open and active.
  2. Whether this is a known bug.
  3. Whether there is a timeout, session renewal, WebSocket, authentication, or background-process issue.
  4. Whether there is a permanent fix or a diagnostic log I can provide.

I can reproduce the issue repeatedly.

Thank you.

]]>https://forums.opera.com/topic/89645/opera-browser-connector-for-chatgpt-repeatedly-disconnects-during-active-useRSS for NodeSat, 26 Sep 2026 23:56:32 GMTThu, 24 Sep 2026 18:44:35 GMT60<![CDATA[Reply to Opera Browser Connector for ChatGPT repeatedly disconnects during active use on Fri, 25 Sep 2026 13:17:52 GMT]]>Update – 25 September 2026

The issue has been reproduced again today.

The Browser Connector was already enabled and connected. No permissions were changed, Opera was not restarted, and no reconnection was performed.

Observed sequence:

  • list-tabs → success
  • next browser operation → failed / tab did not become ready
  • previous reproduction in the same session also returned:
    Browser not connected. Make sure to enable "Allow AI connection"...
  • list-tabs subsequently worked again without any user action

This again indicates an intermittent connector state rather than a permanent disconnection or incorrect setup.

The connection can work, fail on the next operation, and recover without changing settings or reconnecting.

Another user in this thread has independently reported a very similar pattern.

This remains reproducible on Windows 10 with Opera One Stable.

]]>https://forums.opera.com/post/410348https://forums.opera.com/post/410348Fri, 25 Sep 2026 13:17:52 GMT<![CDATA[Reply to Opera Browser Connector for ChatGPT repeatedly disconnects during active use on Fri, 25 Sep 2026 04:25:26 GMT]]>I can reproduce a very similar intermittent connection pattern on Opera One Stable 136.0.6008.52.

Environment:

  • Windows 10 Pro 22H2, OS Build 19045.6456
  • Opera One Stable 136.0.6008.52
  • Browser Connector enabled and already connected to ChatGPT

In a fresh test after the connector was already working, I observed this sequence:

  1. list-tabs -> success
  2. tab-content -> success
  3. list-tabs -> "Browser not connected"
  4. history -> "Browser not connected"
  5. structured tab-content query -> success
  6. list-tabs -> success
  7. tab-content -> success
  8. list-tabs -> "Browser not connected"

I did not reconnect the Browser Connector, change permissions, restart Opera, or sign in again between these calls.

So in my case the connection is not permanently lost: it can fail, recover automatically without user action, and then fail again shortly afterward.

I also reproduced the same behavior before and after updating Opera to 136.0.6008.52.

I have submitted the same finding through Opera's official Desktop Stable bug-report form as well.

]]>https://forums.opera.com/post/410293https://forums.opera.com/post/410293Fri, 25 Sep 2026 04:25:26 GMT