I would like ChatGPT’s integrated browsing experience to support the user’s preferred browser or browser provider, rather than requiring a fixed browser implementation chosen by ChatGPT.
This is different from existing requests to simply open links in the system default browser.
I would still like the webpage to appear inside the ChatGPT app, integrated with the conversation and available to ChatGPT where the user has granted permission. The difference is that users should have the option to use their preferred browser technology/provider underneath that experience, where the operating system makes this possible.
The interaction I have in mind
On mobile platforms, applications can often display web content inside their own UI while relying on browser, WebView, or Custom Tab capabilities provided by the operating system or another browser.
From the user’s perspective, they remain inside the original app, while compatible browser infrastructure handles the webpage.
I would like ChatGPT to offer a similar choice where technically possible.
For example:
In-app browsing provider
- ChatGPT default
- System/default browser provider
- Compatible installed browser/provider
The exact implementation would naturally differ between operating systems depending on the APIs and capabilities they expose.
Why not just open an external browser?
Opening Firefox or another browser as a separate application is useful, and there are already feature requests for that. But it is not the same interaction.
The integrated browser has an important advantage: the webpage remains part of the ChatGPT experience. The user can browse while discussing the page and, with explicit permission, ChatGPT can use the current webpage as context.
I would therefore like to preserve:
ChatGPT UI + integrated webpage + optional shared webpage context
while giving users more control over the browser technology used underneath that experience.
Why browser choice matters
Users may deliberately choose a particular browser because of:
- privacy and security preferences;
- open-source software preferences;
- accessibility features;
- browser-specific settings;
- authentication and session continuity;
- password managers;
- content blocking;
- extensions or other browser capabilities.
For example, some users intentionally use Firefox-derived or fully open-source browsers and may even disable the platform’s default browser.
A separate embedded browser can mean maintaining another browser environment with different sessions, privacy settings, authentication state, and behavior.
Where the platform permits it, allowing ChatGPT to integrate with a user-selected compatible provider could avoid some of that duplication.
Keep the current browser as the default
I am not suggesting removing ChatGPT’s current built-in browser.
For users who prefer the existing experience, nothing needs to change.
This could simply be an additional setting:
Browser provider
- ChatGPT default
- System/default
- Compatible installed provider
If an operating system does not support alternative providers for the required functionality, ChatGPT could fall back to its current browser and explain the limitation.
Permissions should remain explicit
Using another browser provider should not automatically give ChatGPT access to everything that browser can access.
ChatGPT should only receive webpage context when the user has explicitly enabled or approved that sharing.
The choice of browser provider and ChatGPT’s permission to read or interact with webpage content should therefore remain separate controls.
Conclusion
I would like to choose my browser without giving up ChatGPT’s integrated browsing workflow.
The goal is not:
“Always open this link in Firefox instead.”
It is:
“Let me keep browsing inside ChatGPT, but use my preferred browser/provider underneath when the platform supports it.”
This would preserve the convenience of integrated browsing while giving users more control over privacy, browser choice, and open-source software preferences.