[MCP] browser_tabs list/select indices diverge across HTTP sessions with --shared-browser-context
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- devtools, playwright, typescript
- Área
- backend-api-design, devtools
Línea de trabajo
The report is about per-MCP-session tab registry and current-tab state in the browser_tabs tool under --shared-browser-context, so start in the MCP server's session handling and tab-index bookkeeping. Reproduce with two HTTP sessions: create a tab, list it, then select the same index from a new session. Done means indices resolve consistently across sessions or the scoping is documented; the issue has no comments or decision yet, so confirm with maintainers before changing behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment
@playwright/[email protected]- macOS (Apple Silicon), Chrome Stable, Playwright Chrome extension
- Server flags:
--extension --shared-browser-context --background --host 127.0.0.1 --port 8931 - MCP client reaches the HTTP endpoint through an authenticated tunnel; successive tool calls can establish new HTTP MCP sessions.
Observed behavior
With the same extension-backed Chrome browser:
- Tool call:
browser_tabs({action:"new", url:"about:blank"})reports the new tab (e.g. index 1). - Subsequent tool call:
browser_tabs({action:"list"})displays index 1. - Subsequent tool call, under another MCP session ID:
browser_tabs({action:"select", index:1}). - Actual:
Error: Tab 1 not found.
In our test environment the tab exists in Chrome and shows in the returned listing. --shared-browser-context appears to share the underlying browser context without making the tool's per-MCP-session tab registry and current-tab state stable across new sessions.
Control / workaround
Using one persistent upstream MCP session, keeping the same Mcp-Session-Id across calls, the sequence new -> list -> select -> close passes on the same installation. A small single-operator local intermediary that holds one upstream session resolved the symptom.
The intermediary is not safe multi-tenant isolation: unrelated clients should not share unrestricted browser control. We are not asking to grant cross-client tab access implicitly.
Request
Could the behavior be clarified in documentation and/or improved with stable/selectable tab identifiers across reconnects where explicitly authorized? If list results are MCP-session-local, it would help to document the need for a persistent Mcp-Session-Id and avoid giving the impression that positional indices are usable across independently created client sessions.
Related issues
- https://github.com/microsoft/playwright-mcp/issues/1109 — similar list/select inconsistency in 0.0.41 (closed).
- https://github.com/microsoft/playwright/issues/42961 — per-client tab ownership in shared browser contexts.
We can share a minimal HTTP harness if additional reproduction details would help.
- Lenguaje dominante
- TypeScript
- Estrellas
- 100k
- Forks
- 6.9k
- Merge medio
- 16 h 8 min
- PR fusionados (30 d)
- 281
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
microsoft/playwright#44289 ·
Los mantenedores suelen responder en 1 día
-
agent-triage-done
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
microsoft/playwright#44264 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG] WebKit keeps every removed iframe's JS heap alive (memory grows until the page crashes)Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
microsoft/playwright#44290 ·
Los mantenedores suelen responder en 1 día
-
[Regression]: requestFullscreen() in a popup rejects with "not granted" in 1.65 (Chromium 159)Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
microsoft/playwright#44288 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
microsoft/playwright#44287 ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/playwright
Issues similares
-
good first issue
Dificultad 2/5 Medio día Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
blamechris/chroxy#9272 ·
Los mantenedores suelen responder en 1 día
-
no-repo-link tool-submission
Dificultad 1/5 Menos de una hora Aptitud para principiantes 66/100
BraveOPotato/NoSignups#2458 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
drmrd/vernacular#1061 ·
Los mantenedores suelen responder en 1 día
-
[Bug] PUT /profiles/{id} silently drops design_prompt — designed voice profiles cannot be editedAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100