Chrome DevTools MCP
input playground

One form. Real page effects.

Run with the actual MCP server

Specimen 01All submissions intercepted

Does an error leave the field unchanged?

A note that remembers
every keystroke.

Retry note

This page sees the text. Your MCP client sees the tool result. Compare both before retrying.

0intercepted
submits

0recorded
events

No fixture focus

Loading local observer…

JavaScript is needed to intercept submissions and record events. Inputs are disabled. The measured observations and local native runner remain readable.

Bring your own agent.

Manual typing also produces events. This page cannot identify your MCP client or see a tool error. Use a real client or the native runner to connect the call with its effect.

How to target this page with MCP

Open this URL with your own Chrome DevTools MCP client. Choose a specimen.
Call take_snapshot with the current pageId. Use the fresh UID of the labelled field.
Run the input action, then read window.actionFixture.read() with evaluate_script.
Compare the client’s result with the field value and submit count. Exact calls and native runner.

Open the observation book →
9 pinned native cases, including controls and a counterexample.

Chrome DevTools MCP
input playground

A note that remembers
every keystroke.

The Enter key
has consequences.

Two fields.
One active cursor.

A file input
is a specific target.

Bring your own agent.

What actually changed?

Since your checkpoint

Event order

Chrome DevTools MCPinput playground

A note that remembersevery keystroke.

The Enter keyhas consequences.

Two fields.One active cursor.

A file inputis a specific target.

Bring your own agent.

Chrome DevTools MCP
input playground

A note that remembers
every keystroke.

The Enter key
has consequences.

Two fields.
One active cursor.

A file input
is a specific target.