---
title: Can agents try the separate browser first, then use my Chrome?
question: automatic agent browser fallback
area: browser
order: 12
surface: desktop
audience: beginner
visibility: public
keywords: [automatic browser, fallback, separate first, main chrome, shared login, verification, both browsers]
related: [choose-agent-browser-mode, how-do-i-set-up-the-agent-browser, when-does-codus-use-the-agent-browser]
updated: 2026-09-15
---

# Can agents try the separate browser first, then use my Chrome?

In Codus **0.2.184 or later**, choose **Automatic: separate first** in **Settings → Agent browser**. Agents start new pages in the separate browser and can open a page in a dedicated window in your normal Chrome when a browser verification challenge persists or your existing login is needed. Choosing it grants permission for those switches without asking each time. This option is absent from 0.2.183 and earlier.

## Before you start

Both Chrome profiles need their Codus extension connected. Your normal Chrome shares the logins and cookies of the profile where you install its extension. Agents can control only tabs they create; your existing tabs stay private. Using normal Chrome does not guarantee a website will accept an automated visit.

## Set up both browsers

1. Open **Settings → Agent browser** and choose **Automatic: separate first**.
2. Under **Separate browser**, click **Open Chrome to set up** if needed. Follow the displayed **Developer mode** and **Load unpacked** instructions, using that section's folder.
3. Under **Your Chrome**, repeat the setup in your normal Chrome profile, using the different folder shown there. If already installed, reload that extension when Settings requests it. Each installation is done once; changing modes does not mean reinstalling each time.
4. Keep both browsers available. Click **Recheck** to confirm the two connection states. One connected browser does not mean the other is ready.

## What happens during a switch?

The agent explains why it is switching and opens the current page address in its own window within your normal Chrome. The original separate-browser tab remains open. This opens the page afresh: it does not copy cookies, unsaved form fields or previous clicks, and does not repeat a submission. The agent checks the new page before continuing.

New pages still start in the separate browser. An ordinary connection error, rate limit or access restriction does not itself trigger a switch. Research campaigns with their own isolated profiles keep those profiles.

If your normal Chrome or its extension is unavailable, the original tab remains in place. Reopen the profile where you installed the extension, finish the **Your Chrome** setup, and click **Recheck**.

## How do I turn it off?

Choose **Separate browser** or **Window in your Chrome**. New fallback requests are then blocked. Existing agent tabs stay in the browser where they opened, so changing the setting does not interrupt that work.

## How do I know it worked?

The **Automatic: separate first** choice stays selected after reopening Settings. The two setup sections show **Separate browser connected** and **Your Chrome connected** independently. When a page needs a permitted fallback, the agent explains the switch and keeps the original tab open.