Chrome 155 is on the kernel. Try it on one profile first.

Chrome 155 reached the stable channel on 2026-09-23, and the AntiBrow kernel now ships a build of it. New profiles pick it up as soon as the package for their machine is in the release manifest. Existing profiles stay where they are until you move them.

The previous two release notes covered when to move: not all at once on release day, and not so late that the version itself becomes the odd thing about a profile. This one is about the step in between, which is the one people skip.

Why not move a real profile straight away

A new major is a new build of the whole browser, not a new number in the user agent. Rendering, fonts, media and the network stack all come along with it. The fingerprint work on top of that is rebuilt for every major, and the safe assumption is that something you care about can behave differently on the new build until you have seen it behave the same.

A real profile is the worst place to find that out. It carries cookies, logins and history that took time to earn, and every session it runs is part of that history. If something looks wrong, you want it to look wrong on a profile that has nothing to lose.

The one-profile check

Make a throwaway profile and look at it before anything else moves. A new profile already gets the newest build available for your machine, so there is nothing to configure:

import { profile } from 'anti-detect-browser'

const key = process.env.ANTI_DETECT_BROWSER_KEY
const canary = await profile({ key, name: 'canary-155' })
const { page, browser } = await canary.launch()

Then check, in this order:

• It starts and stays up. Open a few heavy pages and leave it running for a while. A crash on the first launch is cheap to discover here and expensive anywhere else.
• It reports what you expect. The user agent and the client hints should both say 155. If they say 154, the package for your machine is not in the manifest yet, and the check waits until it is. The language and time zone should follow the proxy the same way they do on the old major.
• The sites you rely on behave the same. Log in to one of them with a test account if you have one. Pass, challenge or block, the result should match what an existing profile on the same proxy gets.
• Nothing new shows up in a checker. Run the same consistency checks you would run on any profile and compare against a profile on the previous major.

If all four hold, move real profiles in small batches over the following weeks. If one does not, you have lost a throwaway profile and nothing else, and you know not to move the rest yet.

What the check does not tell you

One clean profile is evidence, not proof. It tells you the build works on your machine with your proxy and your sites. It does not tell you how a detector will score a profile that has spent a month on the new major, and it says nothing about proxy quality or account history, which explain far more challenges than the browser version does. The dated detection runs are where we record what actually moved results.

And if you only run one browser for yourself, none of this applies. Your own Chrome updates itself and has nothing to hide by doing so. A managed rollout like this is only worth the effort when you are running many identities that must stay separate.