Chrome extension: Add ability to open incognito windows

Resolved 💬 2 comments Opened Jan 26, 2026 by lucasmccomb Closed Feb 28, 2026

Feature Request

The Chrome extension (mcp__claude-in-chrome__tabs_create_mcp) should support opening tabs in incognito windows for testing logged-out user flows.

Current Behavior

tabs_create_mcp has no parameters and only creates tabs in the normal browser window. There's no way to programmatically open an incognito window or create a tab in an existing incognito window.

Desired Behavior

Add an optional incognito parameter to tabs_create_mcp:

tabs_create_mcp({ incognito?: boolean })

Or add a separate tool:

tabs_create_incognito_mcp()

Use Case

When verifying UI changes, the auth state matters:

  • Logged-in features (admin panels, user dashboards) need the user's session
  • Public features (landing pages, public galleries) should be tested without auth to catch bugs visible to anonymous users

Currently, users must manually open an incognito window before Claude can work with it. Programmatic control would streamline the verification workflow.

Workaround

User manually opens an incognito window, then the Chrome extension can interact with it. But this breaks the automated workflow.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗