The ChatGPT desktop app can browse in two materially different ways. Its built-in browser has its own cookies, history and signed-in state. The Codex Chrome extension can work through the Chrome profile already open on the computer, including its existing accounts, tabs and extensions.[1]
That means “open the website” is not a complete instruction. The same page can present a different customer account, workspace, basket or permission set depending on which browser identity opened it. The choice is part of the task, not a cosmetic preference.
Choose the browser by the state the task needs
| Task condition | Better route | Reason |
|---|---|---|
| Public page or local development site | Built-in browser | Keeps the work inside the desktop app and does not depend on your Chrome profile.Source 1 |
| Existing signed-in account in Chrome | Chrome extension | Can use the active Chrome cookies and session after permission is granted.Source 1 |
| Task depends on open tabs or Chrome extensions | Chrome extension | Those resources belong to the Chrome profile, not the built-in browser.Source 1Source 3 |
| You need site-specific tools exposed inside ChatGPT | Built-in browser | Site tools are available in the built-in browser and may not be available through the extension.Source 2Source 3 |
| The account is sensitive or ambiguous | Stop and verify | The active account and workspace should be checked before any consequential action.Source 1 |
A three-page identity check
Before asking ChatGPT to change anything, open three low-risk pages: the site’s account menu, a page showing the current workspace or organisation, and a harmless record such as a draft or settings screen. Confirm that all three belong to the intended account. This is faster than discovering after a submission that the browser was signed into a personal profile instead of a business one.
- Name the route in the request: “use the built-in browser” or “use my Chrome session.”
- Ask for read-only inspection before a write, purchase, submission or deletion.
- Keep credentials inside the browser prompt; do not paste passwords into chat.
- Review the account name, workspace and final action screen before approval.
Site tools add capability—and another trust boundary
Some sites can expose tools that let ChatGPT interact with the service more directly. That can be useful, but it also means page content and connected functionality may influence the agent. OpenAI advises treating websites as untrusted and keeping the task specific. A malicious instruction embedded in a page should not be allowed to redefine the user’s goal or extract unrelated data.[2]
One sentence that prevents many mistakes
For consequential work, state both the browser and the account: “Use the built-in browser with the project test account,” or “Use my Chrome profile, but confirm the organisation name before continuing.” That small addition turns an implicit and error-prone browser choice into an explicit part of the task.
Sources & further reading
- Using the built-in browser in the ChatGPT desktop app OpenAI Help Center · Accessed 16 Oct 2026
- Using site tools in the ChatGPT desktop app OpenAI Help Center · Accessed 16 Oct 2026
- ChatGPT release notes OpenAI Help Center · Accessed 16 Oct 2026