OpenAI adds Chrome extensions to ChatGPT's desktop browser
Users can install tools such as 1Password, while OpenAI says ChatGPT's agent cannot interact with extensions or their data.
By Ryan Merket · Published
Primary source: James Sun on X
Why it matters
Chrome extensions remove a practical barrier to doing sustained work inside ChatGPT, while the agent-extension boundary will determine whether that convenience survives enterprise security review.

James Sun (@JamesZmSun) said OpenAI added Chrome extension support to the browser inside its ChatGPT desktop app on September 18th, letting users install and pin extensions without moving their work into a separate browser window.
https://x.com/JamesZmSun/status/2100995281097769216
The release turns the in-app browser into a more credible replacement for a conventional work browser. Sun cited 1Password as an example, bringing password management into the same window where a user can ask ChatGPT to browse websites, work across tabs and complete tasks.
Users still have to install extensions inside ChatGPT's browser. OpenAI's documentation for the built-in browser says it maintains its own browser state rather than inheriting a user's Chrome profile, cookies, signed-in sessions or extensions. Cookies created inside the in-app browser persist, Sun said in a reply to the launch thread on X.
That separation matters because OpenAI now offers two routes for browser-based work. The built-in browser keeps the activity inside ChatGPT and supports its own logins, tabs, downloads, passwords and extensions. OpenAI continues to direct users to its Chrome extension when a task requires an existing Chrome profile, open tabs or authenticated sessions already stored in Chrome.
Chrome extension support narrows the cost of choosing the in-app route. Password managers, developer utilities and other browser tools are part of how many users assemble their daily workflows. Requiring a separate, stripped-down browser environment would force them to recreate those workflows or keep switching back to Chrome. OpenAI is removing that objection one extension at a time.
The agent stays outside the extensions
The release also creates an immediate security question: whether an AI agent operating a browser can read secrets held by extensions or use an extension's permissions to reach data that the agent could not otherwise access.
Sun said the current boundary prevents that. In a reply, he wrote that the "agent cannot interact with any shadow dom or extensions," adding that it therefore cannot use an extension to extract information or raise its own privileges. That is OpenAI's description of the product's security boundary, rather than an independent audit of the implementation.
The distinction leaves extensions available to the human using ChatGPT's browser while keeping them outside the agent's control. A person can use a password manager to sign in, for example, without giving the agent direct access to the extension interface. The usefulness of that split will depend on how reliably OpenAI maintains the boundary as browser automation gains more capabilities.
OpenAI's browser documentation separately warns users to treat website content as untrusted, review pages before approving access and enter credentials directly into the browser rather than a chat. ChatGPT asks for approval before using a new website unless the user has previously allowed the host or selected broader permissions.
Enterprise controls follow the browser into work
OpenAI has paired the expanding browser surface with centralized controls for managed deployments. Its enterprise browser policy documentation says administrators can disable the in-app browser, prevent ChatGPT from using websites, restrict browser-history access and block imports of cookies, passwords and browsing history from outside browsers.
Administrators can also set site-level rules for access, uploads, downloads and advanced browser control, and users cannot override those restrictions with their own approvals. Those policies give security teams a way to limit the browser itself even as employees add extensions to their personal workflow inside it.
The extension launch advances OpenAI's effort to make the ChatGPT desktop app the place where work happens, rather than a chat window consulted between tasks. A browser that carries users' preferred tools is harder to dismiss as an auxiliary interface. Keeping the agent away from those tools is the constraint OpenAI has chosen to make that expansion acceptable.