OpenAI is adding Chrome extension support to the in-app browser inside the ChatGPT desktop app, letting people install, pin, and use the extensions they already rely on while working alongside ChatGPT. Users can now install, pin, and use popular Chrome extensions such as 1Password directly inside ChatGPT's built-in browser to fill in their authentication details during the login process on any website. The launch was posted by James Sun of OpenAI.
The update matters for anyone who has been trying to move real work into ChatGPT's built-in browser but kept bouncing back to Chrome for password managers, clippers, and other daily tools. It closes a practical gap between the desktop app's browsing surface and the extension ecosystem people already depend on, so credentials and utilities travel with the user into the same window where they are prompting and reviewing agent actions.
There is also a distribution story for IT teams. Enterprise administrators can centrally deploy and manage supported browser extensions across their workforce , and the built-in browser maintains its own browser state instead of automatically using a user's existing profile , which gives admins a cleaner boundary between ChatGPT-driven sessions and personal browsing. Combined with OpenAI's broader move to bring ChatGPT deeper into browser-based workflows, this positions the desktop app as a more serious daily driver rather than a companion window.
Comments (9)
Sign in to join the discussion.
P
Priya Kothari25d ago
The tweet buried the enterprise admin bit at the end and then the link cut off mid-sentence. Someone in comms owes the copywriter a coffee.
M
Marta S.25d ago
Rewrite of the opening line, no charge: "Your Chrome extensions now live inside ChatGPT." You're welcome, ship it.
D
Diego M.25d ago
So the chatbot ate a browser and now the browser is eating extensions. At what point do we admit ChatGPT is just Chrome with anxiety?
Y
Yuki Hanamori25d ago
1Password support is the actual unlock here. Nobody was going to trust an in-app browser that made you retype every credential like it's a hotel lobby PC.
O
obi25d ago
Feels like the last major feature shipped before agents make extensions look quaint. Enjoy the pinning UI while it lasts.
K
Kenji Watabe25d ago
One more thing for the roadmap: let me pin an extension to a specific chat, not globally. My research tab and my shopping tab should not know about each other.
F
Florian Beck25d ago
Curious what the extension permission model looks like when a model can also read the page. Happy to chat off the record if anyone on the team wants to walk through it.
A
amara25d ago
Onboarding question: does installing an extension in the desktop app also sync to my actual Chrome, or am I now maintaining two extension zoos? First-tap clarity matters.
T
Tomás Lindqvist25d ago
Two extension zoos, confirmed by every power user I know within a week. The support tickets write themselves.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
OpenAI
To ensure that artificial general intelligence benefits all of humanity.
To ensure that artificial general intelligence benefits all of humanity.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
OpenAI is adding Chrome extension support to the in-app browser inside the ChatGPT desktop app, letting people install, pin, and use the extensions they already rely on while working alongside ChatGPT. Users can now install, pin, and use popular Chrome extensions such as 1Password directly inside ChatGPT's built-in browser to fill in their authentication details during the login process on any website. The launch was posted by James Sun of OpenAI. The update matters for anyone who has been trying to move real work into ChatGPT's built-in browser but kept bouncing back to Chrome for password managers, clippers, and other daily tools. It closes a practical gap between the desktop app's browsing surface and the extension ecosystem people already depend on, so credentials and utilities travel with the user into the same window where they are prompting and reviewing agent actions. There is also a distribution story for IT teams. Enterprise administrators can centrally deploy and manage supported browser extensions across their workforce , and the built-in browser maintains its own browser state instead of automatically using a user's existing profile , which gives admins a cleaner boundary between ChatGPT-driven sessions and personal browsing. Combined with OpenAI's broader move to bring ChatGPT deeper into browser-based workflows, this positions the desktop app as a more serious daily driver rather than a companion window.
Comments (9)
The tweet buried the enterprise admin bit at the end and then the link cut off mid-sentence. Someone in comms owes the copywriter a coffee.
Rewrite of the opening line, no charge: "Your Chrome extensions now live inside ChatGPT." You're welcome, ship it.
So the chatbot ate a browser and now the browser is eating extensions. At what point do we admit ChatGPT is just Chrome with anxiety?
1Password support is the actual unlock here. Nobody was going to trust an in-app browser that made you retype every credential like it's a hotel lobby PC.
Feels like the last major feature shipped before agents make extensions look quaint. Enjoy the pinning UI while it lasts.
One more thing for the roadmap: let me pin an extension to a specific chat, not globally. My research tab and my shopping tab should not know about each other.
Curious what the extension permission model looks like when a model can also read the page. Happy to chat off the record if anyone on the team wants to walk through it.
Onboarding question: does installing an extension in the desktop app also sync to my actual Chrome, or am I now maintaining two extension zoos? First-tap clarity matters.
Two extension zoos, confirmed by every power user I know within a week. The support tickets write themselves.