Google Antigravity Chrome bridge

The google antigravity chrome bridge appears during the first-run onboarding flow. After you sign in with a Google account, the app detects any Chrome profiles on the machine and offers to import from them. The import is opt-in, scoped to the profile you choose, and creates a clean copy in the browser's own profile directory. The two profiles remain independent after the import — changes in one do not flow to the other. This page covers every artefact the google antigravity chrome import handles and the edge cases engineers hit most often.

Chromium lineage — why google antigravity chrome compatibility is high

The browser is built on the Chromium open-source project, the same codebase that underpins Chrome. Because google antigravity chrome share a common engine, the compatibility story for web content and extensions is strong: pages that render correctly in Chrome render correctly here, and most Manifest V3 extensions work without modification. The agent runtime and the multi-window orchestration layer sit on top of this Chromium base — they do not replace it or restrict it.

The practical implication for the google antigravity chrome bridge is that the profile formats are compatible at the data level. The browser reads Chrome's SQLite databases for bookmarks and history directly during the import, without requiring a manual export step. The import copies the data and converts it to the browser's own profile schema — Chrome's original files are not modified.

What transfers through the Google Antigravity Chrome bridge

Artefact	Chrome status	Google Antigravity Chrome bridge
Bookmarks	Stored in Chrome profile	Copied at import; placed in "Imported from Chrome" folder
Saved passwords	Stored in Chrome's credential vault	Copied at import if OS keychain access is granted
Cookies	Stored per Chrome profile	Opt-in copy at import; no live sync after
Extensions (MV3)	Installed in Chrome	Reinstallable from the extension store; not copied directly
Browsing history	Stored in Chrome profile	Copied at import; searchable in the browser's history panel
Autofill data	Stored in Chrome profile	Copied at import

Extension behaviour in the google antigravity chrome bridge

Extensions are not copied directly from Chrome's profile directory through the google antigravity chrome bridge. The reason is that extension files include native messaging host registrations, local storage, and cached data that are path-dependent — copying them verbatim into a different profile directory produces broken installations. Instead, the google antigravity chrome bridge records which extensions you had installed in Chrome and presents you with a one-click reinstall list after the import.

For most Manifest V3 extensions, clicking "Reinstall" in the bridge panel opens the extension's page in the Antigravity extension store and installs a fresh copy. The extension starts clean with no imported local storage from Chrome — it behaves as a fresh install. Extensions that use native messaging hosts registered to Chrome's path (such as certain password managers or enterprise security tools) may need their companion desktop app to be reinstalled or reconfigured to register under the browser's own application ID.

Extensions that do not transfer

Manifest V2 extensions that were deprecated in Chrome are also not available in the browser. Extensions that use chrome.* APIs exclusive to Chrome's proprietary layer — a small set — will not function. Any extension that communicates with a local native host registered specifically to Chrome will need the host application to add support for the browser's application ID before it works through the google antigravity chrome bridge.

Cookie and session behaviour

The cookie import through the google antigravity chrome bridge is a one-time operation. After import, the two browsers maintain independent cookie jars. A session you are logged into in Chrome does not automatically appear as a logged-in session in the browser, and vice versa — unless you imported the cookies for that site. This is intentional: keeping the jars separate means the agent runtime can operate in a clean, controlled session without risk of leaking personal site tokens into agent-driven sessions.

For security-conscious teams, this isolation is valuable. The google antigravity chrome bridge gives you a warm start — you are not re-authenticating to every site from scratch — but the agent operates in a profile that is distinct from your personal Chrome session. The NIST AI resource centre covers the broader policy landscape for session isolation in agentic tools.