Are AI browsers Comet and Atlas already dead?
Are AI browsers Comet and Atlas already dead?
Last of three. Comet and Atlas is why a new browser looked inevitable. The move into agents is where the clicking went after Atlas shut down.
Short answer: Atlas is dead, Comet is half-dead, and Chrome's Ask Gemini is what most people actually open now.
Google put the question on the tab. In Chrome, Ask Gemini sits in the toolbar. You opt in once. After that, the current page is the context: summarize it, explain a section, pull the numbers, compare it with other tabs you add. You can attach up to 10 open tabs, or type @ and pick one. While Gemini is using a page, that tab shows a glowing underline. You can stop sharing the page and keep the chat.
This is the feature the AI-browser year kept describing, shipped inside the browser people already use. Google's Chrome help page lists the ordinary jobs: key takeaways, a simpler explanation, a recipe adjusted for a diet, a comparison across pages, a recommendation, a Gmail draft, and multi-step actions on your behalf. It assists when you click it. Incognito stays out.
The dedicated AI browser asked for a new default. Ask Gemini asks for a click on the page you opened for a different reason.
Two products got confused
The 2025 pitch bundled two jobs into one app.
The first job is ask this page. You are already reading. You want a question answered from this DOM, maybe from two other tabs, and you want to stay in the article. That job needs the page in the prompt and a way to say no. It does not need a new rendering engine, a new bookmark file, or a new place to store passwords.
The second job is do this chore. Book the thing, fill the form, pull the report, click through a portal that has no API. That job needs a browser the agent controls, retries, a permissions model, and often computer use for the desktop GUI around the browser: the file dialog, the native app, the login window that is not a webpage.
Comet and ChatGPT Atlas tried to be both, and to be your browser while they did it. Atlas is gone as of 9 August 2026, folded into ChatGPT's desktop app. Comet is still installed for a lot of people, with browser control now metered as Computer credits, and with Perplexity's energy pointed at Computer. The bundle came apart along the seam between the two jobs.
Ask Gemini is Google taking the first job and putting it where the page already is. Chrome's share makes that a distribution decision as much as a model decision. A sidebar in a browser with billions of installs reaches people who will never set a new default.
The chore went to the agents
The second job is having a busy season, and it is not happening in a branded AI browser.
ChatGPT Desktop carries the browser Atlas was. Multiple tabs, downloads, logins, and computer use that can drive Safari when you allow it. The Chrome extension is there when the session you need is the one in your real profile.
Claude Desktop has a built-in Cowork browser in the side panel, separate from your tabs unless you import logins site by site, plus Claude in Chrome for the page you are on. Computer use, in beta for Pro and Max, clicks and types on the desktop when a connector is missing. The desktop app has to be open and awake.
Grok Bot is a cloud computer with a browser already on it, and a person can take over for a login. OpenClaw and Hermes Agent are the self-hosted pair: your machine or your VPS, your model choice, a browser the agent can drive, files and shell beside it. OpenClaw's center of gravity is the gateway into the chats you already have. Hermes's is skills, memory, and scheduled work you can run on hardware you control.
Those five are how "an agent with a browser and computer use" actually ships in late 2026. They are desktops, cloud computers, and local gateways. They are happy to leave Chrome installed. Ask Gemini covers the moment you only wanted to ask. The agent covers the moment you wanted something finished.
What Chrome still does not do
Ask Gemini is a strong reading tool and a light action tool. It can work across the tabs you share with it. It is not a self-hosted gateway, it is not a cloud computer you can close the laptop on, and it is not a place to park a long-running chore with its own credentials. Google's help text includes multi-step actions. The product people open for an afternoon of unsupervised clicking is still the desktop agent, the hosted bot, or OpenClaw and Hermes on a machine they administer.
There is also a trust line worth keeping. Ask Gemini shares page content when you opt in, and you can stop that share. An agent with computer use sees more than the DOM: the screen, the apps, sometimes the password manager's neighborhood. The page-question feature and the computer-use feature should stay easy to tell apart. Chrome's button is the first. The desktop toggle is the second.
Sites will keep treating automated browsers as bots. The March injunction that kept Comet's agents out of signed-in Amazon pages did not expire because the browser brand changed. A cloud browser and a local OpenClaw session hit the same walls when the page is behind a login the site does not want an agent to use. Human takeover, which Grok Bot leans on, is a patch for that wall. It is not a repeal of it.
Same move, on the pull request
Ask Gemini is the pattern worth copying: go to the surface where the work already is, read that surface, and let the person ask. For a code change, that surface is the pull request.
ThinkReview runs on the merge request in GitHub, GitLab, Azure DevOps, and Bitbucket. The model is a choice in Model selection. The finding is a comment on the diff, which is the page the author already has open. An agent that can browse is a different product, for a different afternoon. The review can stay on the request.
Ask Gemini's behavior is from Google's Chrome documentation. The Atlas shutdown and the desktop agents are covered in the previous post. Install ThinkReview.