Reference claude in chrome vs playwright toggle

As of 2026-07-05, claudeInChromeDefaultEnabled in ~/.claude.json was set to false (backup at ~/.claude.json.bak.chrome-playwright). This stops the ~30 always-injected chrome tools (navigate, computer, read_page, tabs_*, etc.) plus their "use these for web tasks" instruction block from auto-loading every session, which had been the cause of agents repeatedly reaching for a disconnected browser extension.

In its place, Playwright MCP (@playwright/mcp) is registered at user scope (all projects) with Chromium pre-installed and smoke-tested (headless launch verified working). This is now the default headless browser tool for agents: no extension, no logged-in-Chrome dependency.

Justin has no Vercel MCP and never did; Vercel was a mistaken assumption on his part (he deploys sites to Cloudflare Pages, not Vercel).

claude-in-chrome (the real, logged-in Chrome) is still available but must be summoned explicitly: either flip claudeInChromeDefaultEnabled back on for a session via /config, or ask Claude to enable it for that conversation. Reach for it only when a task needs Justin's actual authenticated browser session (an authed site headless Playwright can't reach).

Why: Justin was confused why agents kept trying an unconfigured/disconnected browser tool, and wanted Playwright (which he already used via /screenshot//preview-site as a local CLI) to be the real default instead.

How to apply: Don't reach for claude-in-chrome tools by default in future sessions; use Playwright MCP for headless web work. Only invoke claude-in-chrome when the task specifically requires Justin's real, logged-in Chrome, and confirm with him first since it needs the extension reconnected.

[auto-memory session 2e05b6d6-3ee2-4c56-bdcd-14a1528c0c98, confidence 0.85, mode direct]