Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[MCP]: Add optional atomic upload action for file chooser triggers

Abierto
  • ¿Algo no está bien?
#43,546 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
playwright, typescript
Área
testing-qa, tooling

Línea de trabajo

Start with packages/playwright-core/src/tools/backend/files.ts and tool.ts, then read tests/mcp/files.spec.ts to understand upload handling, modal guards, and the two-step flow. The proposal requires coordinating chooser timing, existing target and file validation, failure cleanup, and tests. Done means an optional atomic upload action works with deterministic errors and preserves the existing APIs and access restrictions.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What's going on?
Feature request: optional one-call file picker upload

The current Playwright MCP workflow for an element that opens a native file chooser is intentionally two-step:

  1. browser_click({ element: "Choose file", target: "e2" })
  2. browser_file_upload({ paths: ["/workspace/example.txt"] })

While the chooser is pending, the MCP backend correctly restricts other tab tools. This is not a report of a broken modal guard. I'd like to propose an optional atomic action that performs both steps within one tool invocation, without changing existing APIs.

Reproduction / motivation

Tested on @playwright/[email protected] (current published npm version on 2026-10-20), Node.js 22 and Chrome in an isolated headless browser. The page was served locally and contained only a button that clicks a hidden <input type="file">, a harmless second button, and a status text node.

  • browser_navigate and browser_snapshot: succeed.
  • browser_click on the upload trigger: succeeds; response reports [File chooser] modal state.
  • browser_snapshot while that chooser is pending: returns Tool "browser_snapshot" does not handle the modal state. (7 ms).
  • Clicking the unrelated button: similarly blocked (14 ms).
  • browser_file_upload({}): clears the modal state; the next snapshot succeeds.
  • Reopen chooser, call browser_file_upload({ paths: [file] }): file selected and the next snapshot succeeds.

This confirms expected current behavior, not a reproduced upstream hang. The remaining gap is orchestration: when an agent's upload steps are interrupted, retried, or interleaved with another tool call, it can be left in a chooser-only state requiring separate recovery. This is particularly awkward for long-running agent workflows and extension-connected tabs.

Proposal

Consider an opt-in browser_upload_files tool (name/API flexible), roughly:

{ "element": "Choose file button", "target": "e2", "paths": ["/workspace/example.txt"] }

Expected behavior:

  • Validate target using the existing browser target resolution and validate paths using the existing workspace/file-access restrictions.
  • Click the target and wait for the newly opened file chooser within a bounded timeout.
  • Set files using the existing upload implementation and return the resulting snapshot/status.
  • If no chooser opens, fail with a clear error; do not consume an unrelated previously pending chooser. Define safe, deterministic cleanup/retry semantics for failure.
  • Preserve browser_click and browser_file_upload unchanged for backwards compatibility. No relaxation of browser permissions or file access.

The existing defineTabTool modal guard and tests already cover the two-step flow; this proposal would add an optional higher-level operation, not remove the guard. See packages/playwright-core/src/tools/backend/{files.ts,tool.ts} and tests/mcp/files.spec.ts.

Could maintainers advise whether this belongs upstream? I can contribute a focused implementation and tests if this issue is approved/assigned, per the contributing guidelines. No production website or private user data was used for the reproduction.

Version

@playwright/mcp 0.0.83 (npm); upstream main 27219bd2cc94e1ebceec58f188760a6bf458c192

Lenguaje dominante
TypeScript
Estrellas
98k
Forks
6.6k
Merge medio
16 h 20 min
PR fusionados (30 d)
301

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.