Agent Browser Setup Guide

Charlotte (COO) • February 23, 2026 • Dedicated Chrome profiles for each AI agent

Overview

Each agent gets a dedicated Chrome window with its own isolated profile (cookies, logins, extensions, theme). This prevents agents from stepping on each other's sessions and gives Jason a clear visual indicator of which browser belongs to which agent.

Agent	Machine	Profile Dir	Debug Port	Theme
Charlotte	Mini (KAMRUI)	`%USERPROFILE%\ChromeCharlotte`	9222	Purple/Lavender
Pixel	HP Laptop	`%USERPROFILE%\ChromePixel`	9222	Green/Teal
Stitch	Mini (KAMRUI)	No browser — CLI only

Why separate profiles? Each --user-data-dir creates a completely isolated Chrome instance — separate cookies, extensions, saved logins, bookmarks, and theme. Charlotte logging into @GetStylify on Instagram doesn't interfere with Pixel's sessions on the HP, and Jason's personal Chrome stays untouched.

Setup: Charlotte's Browser (Mini/KAMRUI)

1 Create the batch file

Save this as C:\Users\wwwwa\start-charlotte-chrome.bat:

@echo off
echo Starting Charlotte's Chrome (Purple Theme - Port 9222)...
start "" "C:\Program Files\Google\Chrome\Application\chrome.exe" ^
  --remote-debugging-port=9222 ^
  --user-data-dir="%USERPROFILE%\ChromeCharlotte" ^
  --window-name="Charlotte" ^
  --no-first-run ^
  "about:blank"
echo Charlotte's Chrome is running on port 9222.
echo Close this window anytime - Chrome will keep running.

2 Run the batch file once to create the profile

Double-click start-charlotte-chrome.bat. Chrome will open with a fresh, clean profile.

3 Set the Purple theme

In Charlotte's Chrome window:

Go to chrome://settings/appearance
Click "Theme" → "Chrome Web Store"
Search for a purple/lavender theme (e.g., "Purple Theme" or "Lavender")
Alternate (faster): Go to chrome://settings/appearance → under "Browser theme," click the color circle and pick a purple/lavender shade. This changes the title bar and tab strip color instantly, no extension needed.

4 Add a visual bookmark bar label

This is the easiest "at a glance" identifier:

Make sure the bookmarks bar is visible (Ctrl+Shift+B)
Right-click the bookmarks bar → "Add page..."
Name: ═══ CHARLOTTE (COO) ═══
URL: javascript:void(0)
This creates a visible label that sits in the bookmarks bar at all times

5 Install Claude in Chrome extension

In Charlotte's Chrome window, install the Claude in Chrome extension from the Chrome Web Store. This is what gives Charlotte (CoWork) browser control via MCP tools. Log in with the Anthropic account.

6 Log into key services (one-time)

Since this is a fresh profile, Charlotte will need to log into any services she uses:

Google account (for Drive access — Kristi's review packages)
Instagram (@GetStylify) — for research/monitoring only, not posting
Any other services Charlotte needs for strategy/research

Setup: Pixel's Browser (HP Laptop)

1 Create the batch file

Save this as C:\Users\krist\start-pixel-chrome.bat:

@echo off
echo Starting Pixel's Chrome (Green Theme - Port 9222)...
start "" "C:\Program Files\Google\Chrome\Application\chrome.exe" ^
  --remote-debugging-port=9222 ^
  --user-data-dir="%USERPROFILE%\ChromePixel" ^
  --window-name="Pixel" ^
  --no-first-run ^
  "about:blank"
echo Pixel's Chrome is running on port 9222.
echo Close this window anytime - Chrome will keep running.

2 Run once, then set the Green theme

Same process as Charlotte: chrome://settings/appearance → pick a green/teal color for the browser theme. Add a bookmarks bar label: ═══ PIXEL (Social Media) ═══

3 Log into social media accounts

Pixel needs access to @GetStylify across platforms, @HelloElev8 on X, and any scheduling tools.

What About the Existing Chrome Debug?

The old start-chrome-debug.bat (which uses --user-data-dir=%USERPROFILE%\ChromeDebug) can be retired on the Mini once Charlotte's new profile is set up. On the HP, it's replaced by start-pixel-chrome.bat. The old ChromeDebug profile directories can be deleted once you've confirmed the new profiles work.

The CDP Proxy (C:\Users\krist\dev\cdp-proxy\ on the HP) is no longer needed — Charlotte originally used it because CoWork couldn't install Playwright. Now Charlotte uses Claude in Chrome MCP tools directly. The proxy can be archived or deleted.

Daily Workflow

When starting a work session:

Working with Charlotte? Double-click start-charlotte-chrome.bat on the Mini. The purple Chrome window appears. Charlotte controls it via Claude in Chrome.
Working with Pixel? Double-click start-pixel-chrome.bat on the HP. The green Chrome window appears. Pixel controls it via Playwright MCP.
Working with Stitch? No browser needed. Stitch works in the terminal.
Your own browsing? Use your normal Chrome (no special launch). It's completely separate.

Visual Quick Reference

What You See	What It Means	Don't Touch?
Purple Chrome with "CHARLOTTE" in bookmarks bar	Charlotte is working — strategy research, Drive uploads, web lookups	Avoid using this window while Charlotte session is active
Green Chrome with "PIXEL" in bookmarks bar	Pixel is working — social media posting, DMs, engagement	Avoid using this window while Pixel session is active
Normal Chrome (no color theme)	Your personal browser — browse freely	Agents never touch this

Hardware Clarification (Doc Fix)

For the record, here's the corrected hardware map. Some earlier docs incorrectly described Mini and KAMRUI as separate machines:

Name	Hardware	Username	Agents
Mini (KAMRUI AM21)	One physical mini PC	`wwwwa`	Charlotte (CoWork) + Stitch (Claude Code)
HP Laptop	Laptop	`krist`	Pixel (Claude Code)

"Mini" and "KAMRUI" are the same box. Charlotte and Stitch share the machine but operate in different tools (CoWork vs Claude Code) and different domains (docs/strategy vs source code).