Proposal: let an MCP client label its own tab group (browser_set_group_label)
Los mantenedores suelen responder en 1 día
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Motivation
Once multiple simultaneous MCP client connections are supported (#41838), a user running several
agents at once against the same browser has no easy way to tell which Chrome tab group belongs to
which task or agent - each just shows as "Playwright" (or "Playwright · " under
#41838), which isn't always meaningful (e.g. several connections from the same client name/tool,
or a generic name that doesn't describe the task).
This is also mildly useful even with a single connection - a user can see at a glance what an
agent is currently working on from the tab group's title, without switching to the agent's
terminal/window.
Proposed tool
A new MCP tool, browser_set_group_label, letting an agent set a short custom label for its own
connection's tab group early in a task:
browser_set_group_label({ label: "checkout flow bug" })
This renames the connection's tab group to Playwright · <label> (deduplicated with a (2),
(3)... suffix if another active connection already used that exact label). The tool's own
description would suggest calling it once, early, especially when the user might be running the
agent alongside others - since MCP tools are discovered by their description, not by hardcoded
client-side instructions.
Scope
Touches both the extension (packages/extension, applying the label to the actual Chrome tab
group) and the server (packages/playwright-core/src/tools, a new MCP tool + a small new
session-level protocol command distinct from the existing CDP-passthrough commands). No protocol
version bump needed if kept backward compatible with clients that don't call it.
I have a working implementation and test coverage for this already, built on top of the
multi-connection work in #41838 (though the tool would still have narrow value even without it,
for the "what is this agent doing" case). Wanted to check whether this is a direction the team
would want before opening a PR, per the contribution guidelines - happy to adjust the shape of the
tool (naming, whether it belongs in core capability, etc.) based on feedback.
- Lenguaje dominante
- TypeScript
- Estrellas
- 99.1k
- Forks
- 6.8k
- Merge medio
- 15 h 48 min
- PR fusionados (30 d)
- 322
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
-
[Bug]: getByLabel (and accessible name) ignore <label> for form-associated custom elementsPosiblemente ocupada @microsoft-playwright-automation la tomó hace 1 día. Abiertoneeds-triage
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
microsoft/playwright#43898 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
[Feature]: Option to make all locators ignore hidden elements by defaultPosiblemente ocupada @microsoft-playwright-automation la tomó hace 1 día. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
microsoft/playwright#43855 · 6 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Feature]: Configure web servers per projectPosiblemente ocupada @microsoft-playwright-automation la tomó hace 2 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoft/playwright#43853 · 4 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
[Feature]: Extend isVisible/toBeVisible API to include overlap detectionPosiblemente ocupada @microsoft-playwright-automation la tomó hace 2 días. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
microsoft/playwright#43849 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Bug]: connectOverCDP: a tab whose main frame was swapped in by a prerender never initializes, and title()/evaluate() hang forever (default Chrome/Edge settings)Posiblemente ocupada @dgozman la tomó hace 3 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
microsoft/playwright#43842 ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/playwright
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/durable-harness#53 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Redesign tab bars ignore clicks on Linux: hidden chat layers keep window drag regionsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
area/docs area/ui enhancement
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
melgarafael/DeskcommCRM#4098 ·
Los mantenedores suelen responder en 1 día
-
bug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
kerti/balances-v2#801 ·
Los mantenedores suelen responder en 1 día
-
lesson-submission pending-review
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Ikalus1988/MisakaNet#4510 ·
Los mantenedores suelen responder en 1 día