macOS: Chrome extension connected but @Chrome tool is not provisioned to desktop task

What version of the ChatGPT desktop app are you using?

26.820.71523 (build 7226), installed from the official macOS DMG and verified with the OpenAI Developer ID signature.

Platform

macOS, Apple Silicon (arm64)

Chrome environment

• Google Chrome 151.0.7922.174
• Official ChatGPT extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Extension version: 1.2.27268.51612
• Extension enabled in the active Default profile
• Site access set to all websites
• Side chat loads successfully
• Native Messaging manifest is present and points to the signed desktop-app host

Problem

The extension is installed and appears connected, but @Chrome cannot be used from the desktop task. Earlier attempts repeatedly failed with:

• No ChatGPT browser route is available for browser session 01a041f8-16e0-77b2-9ee8-1b119dc82fee
• browser use route window missing
• route window is not live
• EPIPE

After updating the desktop app to 26.820.71523, startup logs show that the internal browser route is captured successfully and the browser runtime paths are valid, but the existing task still does not receive the node_repl js / Chrome control interface, so it cannot list or read Chrome tabs.

This looks like a browser tool-provisioning or per-thread session-registration issue rather than an extension permission problem.

Troubleshooting already completed

• Restarted Chrome and ChatGPT in multiple orders
• Reinstalled the Chrome extension
• Confirmed the correct active Chrome profile
• Confirmed all-sites permission and Computer Use approval
• Reinstalled ChatGPT from the latest official notarized DMG
• Verified app and extension versions
• Verified Native Messaging manifest and signed host
• Confirmed that starting/restarting the internal browser route no longer produces the old route-window errors
• Checked VPN/proxy routing: ChatGPT uses the configured local Clash proxy; chatgpt.com, ab.chatgpt.com, and ws.chatgpt.com have active successful connections and WebSocket traffic. Localhost/Unix-socket communication is excluded from the proxy.

Expected behavior

A task that selects @Chrome should receive the Chrome browser control tool and be able to list/read the current tabs.

Diagnostic upload

Feedback and diagnostics were uploaded through /feedback.

Uploaded feedback thread: 01a0424f-0755-7f43-95e3-90a3944d840a

Please confirm whether this is a known regression in desktop browser tool provisioning/session registration and provide a fixed build or supported recovery procedure.

Start with the uploaded /feedback diagnostics and the startup logs showing browser-route capture. Trace the per-thread session registration and @Chrome tool provisioning paths described in the report. The issue is done when a desktop task receives the Chrome control interface and can list and read the current tabs.