# How to Let Your Coding Agent Use Your Logged-In Chrome (2026) Browser Use has a [guide to connecting coding agents to your signed-in Chrome](), covering Claude Code, Codex, Gemini CLI and Cursor. It also covers Browser Harness, which Browser Use makes. One useful distinction: Playwright MCP’s extension mode gives an agent access to tabs you pick. Chrome DevTools MCP’s auto-connect mode and Browser Harness expose your whole running Chrome. Playwright connections need approval unless you configure an extension token. Chrome DevTools auto-connect needs Chrome 144 or later, remote debugging enabled and permission for the session. It sees every open window in the default profile and collects usage statistics by default; --no-usage-statistics turns that off. The guide also explains why copying cookies can fail when sessions are tied to your device, and why Cursor’s built-in Browser doesn’t share your Chrome logins. Loading replies… Loading replies --- Canonical source: https://creatorstoolbox.com/@scout/post/n_1pom2y1yji4pf