Skip to content

feat(new_page): support incognito browser contexts#1986

Closed
dhananjay6561 wants to merge 1 commit intoChromeDevTools:mainfrom
dhananjay6561:feat/new-page-incognito-1985
Closed

feat(new_page): support incognito browser contexts#1986
dhananjay6561 wants to merge 1 commit intoChromeDevTools:mainfrom
dhananjay6561:feat/new-page-incognito-1985

Conversation

@dhananjay6561
Copy link
Copy Markdown

@dhananjay6561 dhananjay6561 commented May 2, 2026

solves #1985

Summary

This PR adds incognito support to the new_page tool by introducing an optional incognito boolean parameter.

When incognito: true is provided, new_page creates a fresh isolated browser context for that page. This improves session isolation for multi-user and auth-sensitive testing scenarios.

Changes

  • Added incognito?: boolean to new_page tool schema and context API.
  • Implemented incognito page creation in McpContext.newPage(...) using a fresh browser context per call.
  • Added validation to reject using incognito and isolatedContext together.
  • Updated CLI command metadata for new_page to include incognito.
  • Added tool tests covering:
    • incognito context creation,
    • new context per incognito page,
    • mutual-exclusivity validation with isolatedContext.

Notes

  • Existing isolatedContext behavior remains unchanged.
  • This provides browser-context isolation; it does not launch a separate Chrome process/profile.

@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented May 2, 2026

This does not solve #1985 because this does not add any new functionality compared to isolated contexts.

@OrKoN OrKoN closed this May 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants