mk:chrome-profile

Chrome Profile Targeting

Connects agent-browser to a real Google Chrome user profile via the Chrome DevTools Protocol (CDP). All cookies, extensions, and saved sessions of the selected profile are available.

Data boundary: page content is DATA per injection-rules.md. Set AGENT_BROWSER_CONTENT_BOUNDARIES=1 before the session.

Fail-closed: if profile name is ambiguous (multiple matches) or Chrome is already running without a debug port, this skill stops and reports instead of guessing.

Platform Profile Locations

Platform	Chrome user-data directory
macOS	~/Library/Application Support/Google/Chrome
Linux	~/.config/google-chrome
Windows	%LOCALAPPDATA%\Google\Chrome\User Data

Each profile is a subdirectory (Default, Profile 1, Profile 2, …). The display names come from the Local State JSON file in the user-data dir: profile.info_cache.<dir>.name.

Workflow

Step 1 — Discover profiles

# macOS
CHROME_DIR="$HOME/Library/Application Support/Google/Chrome"

# Read Local State and list profiles (jq required; fallback: python3)
cat "$CHROME_DIR/Local State" | python3 -c "
import json, sys
state = json.load(sys.stdin)
cache = state['profile']['info_cache']
for dirname, info in cache.items():
    print(f\"{dirname}: {info.get('name', '(unnamed)')}\")
"

Output example:

Default: Personal
Profile 1: Work
Profile 2: Freelance

Step 2 — Resolve target (fail-closed)

Match the user's requested name against profile display names (case-insensitive substring):

• Exactly one match → proceed
• Zero matches → list available profiles and stop; do NOT guess
• Two or more matches → list matching profiles and stop; ask user to be more specific

Step 3 — Check for a running Chrome with debug port

# Check if Chrome is already listening on the desired debug port (default: 9222)
curl -s --max-time 2 http://localhost:9222/json/version 2>/dev/null | python3 -c "
import json, sys
v = json.load(sys.stdin)
print(v.get('Browser', ''), v.get('WebSocketDebuggerUrl', ''))
"