wait_for can match visible text
Introduced 2026-10-22 · score 0.97
HOW TO USE IT
When testing a page interaction, wait for the confirmation text to become visible. Call `wait_for` with `visible: true`, a non-empty `text` list, and the target `pageId`.
wait_for({pageId:<pageId>,text:["Saved successfully"],visible:true,timeout:5000})WHY THIS HELPS
Wait for a visible confirmation message while testing a page interaction.
BEFORE THIS CHANGE
Before this change, `wait_for` could resolve on text in the DOM even when it was hidden; the prior behavior remains when `visible` is omitted or false.
REQUIREMENTS AND LIMITATIONS
- Version: 1.12.0
- pageId (required): Page ID to target.
- text (required): Non-empty list of strings; resolves when any listed text appears.
- visible: When true, wait until matching text is visible; otherwise hidden text also counts.
- timeout: Maximum wait in milliseconds; 0 uses the default timeout.
- Prerequisite: Chrome DevTools MCP requires Node.js LTS, npm, and current stable Chrome or newer.
- Visible-text matching is opt-in.
- By default, hidden text also counts.
- Docs conflict: The release-note example omits `pageId`, but the v1.12.0 tool reference marks it required.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v1.12.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/3212
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v1.12.0/docs/tool-reference.md
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v1.12.0/README.md
Check the installed version and the source before using it. Entry JSON