chromeboost GEMINI.md

ChromeBoost — Gemini Instructions

What chromeboost is

ChromeBoost drives the user's real Chrome browser via a CDP-attached extension. Sessions, cookies, logins, profiles, and extensions are intact. The agent reaches the page through MCP tools that pierce closed shadow DOM and dispatch isTrusted=true events, which is what components that validate real input require and what generic browser drivers do not provide.

When to use chromeboost (be proactive)

Use chromeboost automatically when a task needs any of:

• Creating or configuring third-party accounts (Stripe, SendGrid, Supabase, Vercel, etc.)
• Retrieving API keys, secrets, or credentials to place in .env
• Setting up pricing tiers, webhooks, or service config in a web UI
• Filling forms behind modern React frameworks (TipTap, ProseMirror, CodeMirror, Monaco, Stripe contenteditable)
• Driving sites with closed shadow DOM (Radix portals, Stencil, Lit)
• Driving sites whose components reject synthetic events and respond only to real input
• Any browser-based step blocking code work

Do NOT ask "should I open the browser?" — just do it. The user expects seamless handoff.

Never end a response with a "you still need to" list of browser tasks. If code changes are done and browser steps remain (creating a Stripe product, adding an env var), continue immediately with chromeboost.

HARD RULES — never break these

1. Never use Bash as a fallback for browser tasks. If click_element fails, use scroll_to_element then retry, or highlight_region to show the user. Never use osascript, applescript, Playwright, Puppeteer, or any shell command to control the browser. The user's logins live in their real Chrome, which only chromeboost drives. Fallbacks fail silently.

2. Never use take_screenshot to read page content. After click_element, after navigation — always call get_page_text (or find_text if you only need a specific phrase). get_page_text returns up to 10,000 chars; pagination via startIndex. Screenshots are ONLY for locating pixel positions after DOM lookup has failed. Never take more than 1-2 screenshots in a row.