Choose the browser workflow that fits your work.
AI browsers bring their own assistant. Customaise brings tools for the agent you choose, in the Chrome you already use.
By Customaise · Reviewed
Covers current documented ChatGPT browser tools, Comet and Dia, alongside Customaise 1.3.9. OpenAI retired Atlas on 9 August 2026; its browsing moved into the ChatGPT desktop app and extension. This page does not promise Customaise compatibility inside other browsers.
Access: Check the browser path
A new browser, a built-in browser and an extension using existing tabs are different setups.
Scripts: A managed library
Customaise keeps UserScripts and AgentScripts available with enablement and permission controls.
Context: Check each feature
What a provider receives depends on the requested task and enabled capabilities.
Side-by-side comparison
| Capability | Customaise | AI browsers |
|---|---|---|
| Browser setup [9] [1] [2] [3] [4] | Install in supported desktop Chrome and connect the agent you choose. | ChatGPT offers built-in and existing-browser paths. Comet and Dia have their own browser setup. |
| Platform availability [8] [1] [3] [4] [5] | Features depend on supported Chrome and device capabilities; not every Chromium variant is verified. | Comet documents Mac, Windows, iOS and Android. Dia documents Mac and Windows. ChatGPT browser features depend on the desktop app, browser and rollout. |
| Existing website sessions [9] [1] [2] | Uses the connected browser profile; sites can still require authentication. | ChatGPT’s extension can use existing signed-in tabs. A separate browser/profile may require its own sign-ins. |
| Userscript support [8] [3] [6] | Full Tampermonkey parity on Chrome: every GM API and metadata key it supports there, with ZIP and JSON backup import. | Comet and Dia document extension support. No built-in userscript manager does not mean userscripts are impossible. |
| Customaise and third-party script managers have not been exhaustively tested inside these alternative browsers. | ||
| Reusable agent tools [9] [1] [14] | AgentScripts expose named tools through Customaise’s MCP and CLI bridge. | Saved instructions, site tools and integrations differ by product. ChatGPT supports WebMCP only in its built-in browser, in Work and Codex, with GPT-5.6 Sol or GPT-6 Sol. |
| How the agent acts [9] [13] [1] [3] [6] | Uses installed tools or requests page context; optional supported DevTools operations are available. | Capabilities depend on the product and its browser tools; no universal consumer-site or internal-dashboard success rate is established. |
| Page context and privacy [12] [2] [7] | Data sent through your agent and optional cloud features depends on what you enable. | Read each product’s policy. Comet describes local storage and task-dependent use of browsing context; ChatGPT documents browser context entering the conversation. |
| Agent choice [9] [1] [3] [6] [15] | Claude Code, Cursor, Codex, Kiro, Antigravity and Claude Desktop over MCP; Grok Bot and any shell agent over the CLI. Power User can also run the in-browser AI on your own key or your own model server (llama.cpp, Ollama, LM Studio, vLLM). | The integrated assistant belongs to the chosen product; extension and connector options vary. |
| AI decisions in scripts [10] [1] [3] [6] [15] | Free on-device AI with CM_promptAI (Gemini Nano, no key, Chrome 148 or later). Power User adds Script Decisions with Jev, OpenAI Decisions API or Gemini Decisions API. | An assistant’s reasoning is separate from Customaise’s per-script decision-provider setup. |
| Control and maintenance [9] [1] [7] | Review scripts, tool permissions and URL scope; repair assumptions when a site changes. | Use the product’s access and task controls and check the result; assistant behaviour also depends on site changes. |
| Choosing a plan [11] [1] [3] [4] | Free bridge limits and optional Power User; external model/provider costs are separate. | Plans, feature access and rollout differ by provider. Check the product’s current access information. |
What is the real difference?
“AI browser” covers several products and connection models. OpenAI documents both a built-in browser and an extension for existing browsers. Comet and Dia combine their browser experience with assistant features. These are not one uniform architecture or privacy policy.
Customaise is useful when you want a script library for your own page controls and your agent’s named actions. It works in the Chrome you already use, with its sign-ins, and runs your userscripts with full Tampermonkey parity.
Current products, not an old launch snapshot
Dia’s Windows changelog includes its October 2026 launch. Comet’s March 2026 announcement includes mobile platforms. For OpenAI, this page uses current ChatGPT browser documentation; OpenAI retired Atlas on 9 August 2026. [1] [4] [5] [16]
Extensions are not a compatibility guarantee
A browser supporting Chrome extensions is different from every extension feature working there. Test the script engine, permissions and any local-model requirements you need. [8] [3] [6]
Separate the data routes
Scripts execute in the browser. Your external agent receives the context and results you give it. Optional cloud AI, Script Decisions, remote approvals and sync have separate data flows; using the local bridge does not make the whole product offline. [12]
AI in your scripts
CM_promptAI runs Gemini Nano on the device, free and with no key, in Chrome 148 or later. Power User adds Script Decisions: focused classification or scoring with Jev, OpenAI Decisions API or Gemini Decisions API, declared in the script with @grant CM_decisions and run with a saved provider key on an authorised device. Provider charges are separate. [10] [15]
When should you use which?
Customaise
You want to keep browser customisations and reusable agent actions in an extension-managed script library.
AI browsers
You prefer a browser’s integrated assistant or ChatGPT’s browser tools and do not need Customaise’s script-management workflow.
An assistant and a script manager may complement each other where compatible. Check the actual browser, extension support and connection rather than assuming automatic integration.
Sources and scope
Covers current documented ChatGPT browser tools, Comet and Dia, alongside Customaise 1.3.9. OpenAI retired Atlas on 9 August 2026; its browsing moved into the ChatGPT desktop app and extension. This page does not promise Customaise compatibility inside other browsers.
By Customaise. Product capabilities are based on documentation and our implementation. Recommendations are workflow judgments, not a head-to-head performance or security benchmark.
- [1] OpenAI: current ChatGPT browser modes and site tools
- [2] OpenAI: browser extension and existing sessions
- [3] Perplexity: Comet setup and Chrome extensions
- [4] Dia: Windows changelog
- [5] Perplexity: March 2026 platform release
- [6] Dia: Mac changelog and extension support
- [7] Perplexity: Comet data and privacy
- [8] Customaise: UserScripts
- [9] Customaise: AgentScripts and permissions
- [10] Customaise: Script Decisions
- [11] Customaise: plans and allowances
- [12] Customaise: privacy and data flows
- [13] Customaise: DevTools access
- [14] OpenAI: WebMCP in ChatGPT
- [15] Customaise: on-device AI and your own models
- [16] OpenAI: ChatGPT release notes (Retiring Atlas)
Related comparisons
- Customaise vs Tampermonkey: Compare a userscript manager with Customaise’s integrated workflow for building, testing and reusing UserScripts and AgentScripts.
- Customaise vs Playwright: Playwright automates browsers from code. Customaise adds named tools and page controls to the Chrome you already use.
- Customaise vs Browser Use: Browser Use offers local and cloud paths, including Browser Harness. Customaise centres the workflow on an installed library of scripts and tools.