dialog - kubed-io/selenium-flow GitHub Wiki

dialog

Answer a native alert, confirm or prompt: accept, dismiss, read (see the message without answering), or send_text (fill a prompt with text and accept it).

MCP tool dialog
HTTP POST /browser/dialog

An open dialog blocks every other command, so if a call fails on an unexpected alert, clear it here.

Parameters

Name Type Required Default
action string no accept
text string no —
wait_timeout integer no 10

Every call names its workspace: an X-Workspace header, or ?workspace=<name>. Sending both is refused. See Workspaces.

Returns

Field Type Notes
action string What was done with the dialog.
message string The dialog's text, read before it was answered.
url string Current URL after the action.
title string Page title after the action.
site_data object Present only when site data was restored, skipped or forgotten in this call.
page object Present only when this browser was opened with capture=true and the page reported a failure while the call ran: what it caused, and where to read it.

Errors

Status Means
400 The request cannot succeed as sent — a missing field, a value that was rejected, or a locator that matched nothing before the wait ran out. Do not retry it unchanged.
401 Missing or wrong bearer token.
404 No such browser session. It ended, the Grid reaped it, or the id was never real. Open a new one and retry.
413 The body is over its cap: 1 MiB of JSON, 64 MiB of upload, 1 MiB of flow YAML. Send less; retrying it unchanged will fail again.
500 Something failed that this server did not expect.
503 The Grid could not serve this — unreachable, or no free slot for a new browser. Worth retrying after a wait.

Over MCP the same failures arrive as a tool error.

Example

MCP

dialog()

HTTP

curl -X POST $SELENIUM_FLOW/browser/dialog \
  -H "Authorization: Bearer $TOKEN" \
  -H "X-Workspace: $WORKSPACE"

← All actions · Installing · Deployment

⚠️ **GitHub.com Fallback** ⚠️