/chatgpt-web-research

name: chatgpt-web-research
description: Use the user's already signed-in official ChatGPT website account, especially GPT-5.5 Pro / ChatGPT Pro, to perform product research, market research, competitor research, second-opinion research, or any browser-only work. Load chrome:control-chrome first, then computer-use:computer-use for fallback. Save verified Markdown reports. Do not use free-account routes, OpenAI API, local models, web search, or memory when the real ChatGPT web page is available.

ChatGPT Web Research

Hard Rule

Use the official ChatGPT web page through the user's already signed-in Chrome account/profile as the source of truth.

Do not create or use a separate free ChatGPT window/account. If the intended Pro / GPT-5.5 Pro account is not visibly available through either the Chrome plugin-controlled page or the Computer Use fallback, stop and ask the user to open or switch to the correct account.

Do not answer from the OpenAI API, local model output, ordinary web search, the deprecated `chatgpt-web` MCP, old task files, or memory. If the Chrome plugin route is unavailable in the current threat model, switch to Computer Use only after confirming it can operate the visible ChatGPT window/tab.

When the task is product or market research, the deliverable is not complete until the ChatGPT web response is visibly complete, extracted from the page, saved as Markdown, and verified.

Required Routes

Before browser-plugin work, load and follow `chrome:control-chrome`. Before Computer Use fallback work, load and follow `computer-use:computer-use`.

• Load `chrome:control-chrome` from the current environment skill registry. Do not hard-code user-specific local plugin paths.
• Load `computer-use:computer-use` from the current environment skill registry before Computer Use fallback. Do not hard-code user-specific local plugin paths.
• If the Chrome skill body was included verbatim in the current user message, it does not need to be re-read.
• Prefer the Chrome skill's `node_repl` / browser-client route when available.
• Do not blindly use `agent.browsers.get("extension")` when more than one Chrome extension instance/profile is available. First call `agent.browsers.list()`, inspect only the returned metadata such as profile name or visible window title, and match that against the user's request or visible Chrome window.
• Start by inspecting Chrome tabs through the selected browser's `browser.user.openTabs()` and claiming a real ChatGPT tab from the user's existing Chrome session whenever one is available. This is faster and preserves the user's signed-in context and conversation history.
• Do not inspect cookies, local storage, passwords, browser profiles, or session stores.
• If `node_repl` is not visible, use tool discovery for `node_repl js`. If it still is not available, switch to Computer Use fallback.
• Treat `Browser is not available: extension`, `Browser is not available: iab`, an empty `agent.browsers.list()`, or an inability to claim the visible ChatGPT tab as Chrome-plugin failure. Do not retry the same path; switch to Computer Use fallback and operate the visible Chrome window instead.

Computer Use Fallback

Use this path only after the Chrome plugin route is unavailable or cannot attach, or when the user explicitly asks for `@电脑`.

• Control the user's already-open Chrome window/profile. Prefer the window whose title, profile button, and tab strip match the intended account/profile, for example `Chrome - <profile-name>`.
• It is acceptable to open a new ChatGPT tab in the same verified Chrome window/profile when the user approves or the current verified tab is unsuitable. Do not open a different Chrome profile or window that could use a wrong account.
• Use only visible page information for account/model checks. Do not open or inspect session/status endpoints, cookies, local storage, passwords, browser profiles, or session stores.
• If a sensitive session/API tab is already open, ignore it and do not quote or extract its contents.
• Confirm GPT-5.5 / Pro by opening the visible model/menu when needed and checking labels such as `GPT-5.5`, `Pro`, `Pro 扩展`, or an equivalent paid-route indicator. If Pro status cannot be confirmed from the visible page, stop and ask the user to verify the Pro model in their Chrome window before continuing.
• Use the visible ChatGPT composer to paste or set the prompt. Verify the unique completion marker appears in the composer before sending.
• Use the same completion criteria as the Chrome route: wait until the page is no longer generating and the visible response contains the marker.
• Prefer the page's `复制回复` button for extraction, but verify the system clipboard contains non-empty assistant text with the marker. If the page shows `Failed to copy to clipboard`, the clipboard may not be accessible; try DOM extraction next.
• If Computer Use focus lands on unrelated tabs, switch back by exact ChatGPT tab title/URL and do not read unrelated private content.

Workflow

1. Name the browser session, for example `🔎 ChatGPT 调研`. 2. Locate the intended ChatGPT account through the Chrome plugin:

• Call `agent.browsers.list()` and identify all Chrome extension instances. If the user names an account/profile such as `<profile-name>`, match that name before opening or claiming any ChatGPT tab.
• If multiple Chrome instances are visible and none matches the user's named account/profile, do not fall back to the last-used or default Chrome profile.
• If the user says the named Chrome profile/window is already open, use `computer-use` only to inspect the visible Chrome window title, profile button, tab strip, and Codex extension presence. Do not inspect profiles, cookies, or browser storage.
• Call `browser.user.openTabs()` on the selected Chrome instance and look for existing `chatgpt.com` tabs.
• Prefer a tab whose visible title/account/model indicates the user's paid ChatGPT account.
• Claim the exact tab object r