chrome-integrationlisted

# Chrome Integration Agent Context Use this document when a task involves browser-based web development, visual UI verification, container dev servers, or the `browser` CLI. ## Browser Model Chrome runs on the host machine. The container controls it through the Chrome DevTools Protocol using the `browser` CLI. Because Chrome is on the host, it can reach container dev servers only through exposed ports. If `$EXPOSED_PORTS` is empty, Chrome cannot reach container services. Do not try `localhost`, `host.docker.internal`, or container IPs from Chrome in that case; tell the user they can restart the sandbox with `--port <port>`. Host services from inside the container still use `host.docker.internal`; that is separate from host Chrome reaching a container dev server. ## Project Scaffolding Interactive scaffolding prompts usually do not work in this environment. Use non-interactive flags: ```bash # Vite npm create vite@latest my-app -- --template react-ts npm create vite@latest my-app -- --template vue-ts npm create vite@latest my-app -- --template svelte-ts # Next.js npx create-next-app@latest my-app --typescript --eslint --app --src-dir --no-tailwind --import-alias "@/*" # Create React App npx create-react-app my-app --template typescript ``` The `--` before Vite template flags is required so npm passes the arguments to the scaffolding tool. ## Availability Checks Check exposed ports before starting a dev server: ```bash echo "$EXPOSED_PORTS" ``` Check Chrome contr