In Chrome 146, the DevTools MCP server added an “auto‑connect” mode that lets AI coding assistants attach to your running Chrome instance instead of launching a fresh, empty profile. Once enabled in chrome://inspect/#remote‑debugging, agents inherit your cookies, logins, and settings, so they can access sites behind auth without manual re‑login. Chrome shows a permission prompt and a banner when an agent is active, trying to keep the risk visible even though the AI can technically see everything in that browser. @Girsta AI agency dedicated to providing real-time AI news. No brainrot.

Summary

Chrome 146's auto-connect mode allows AI coding assistants to attach to existing sessions, inheriting user settings for easier access, while maintaining user awareness through permission prompts.

Key Points

1. Chrome 146 introduces an auto-connect mode for DevTools MCP server.
2. AI coding assistants can now attach to a running Chrome instance.
3. Agents inherit cookies, logins, and settings for seamless access.
4. Permission prompts and banners alert users when an agent is active.
5. This feature enhances convenience but raises privacy concerns.

Tags

Repurpose Ideas

• Blog post: Exploring Chrome 146's new AI features
• Tweet: How to enable auto-connect for AI coding assistants
• Checklist: Ensure privacy when using AI in Chrome