Command reference

Every command is written as for agent-browser. A checkpoint records output; the others act. A selector is CSS unless the command is find.

Every action waits up to the action timeout (5 s) for its element: visible and enabled for input, visible for hover. An action that starts a navigation waits for the new page's load.

An action that presses a point (click, dblclick, hover, check, uncheck, the source of drag) also waits until the element at that point is the target, something inside it, or the label of the control it is. A modal or banner that covers it, a point off the screen, or a menu that is clipped away is waited out like any other state, and when it stays the step fails at the click, saying what is there:

Timed out after 5s waiting for role link --name "Quick reference" --exact to receive a click at (84, 412): <div#cookie-banner.banner> would receive it instead.

An element with pointer-events: none is passed through, as a real click does. The Playwright runner gets the same check from Playwright, whose actions wait to "receive events".

find role|text|label|placeholder|alt|title|testid <value> [click|fill|check|hover|text] [text] [--name <name>] [--exact]
find first|last <sel> [action] [text]
find nth <n> <sel> [action] [text]

• role matches the accessibility role; --name its accessible name.
• text, label, placeholder, alt and title compare as a case-insensitive substring with whitespace collapsed, or whole and case-sensitive with --exact. testid matches data-testid exactly.
• Without an action, find clicks, as agent-browser's does. find … text is a checkpoint: the element's text.

All checkpoints.

All checkpoints. See checks and performance.

Assertions, after Playwright's. An expect line checks again and again until it holds or the timeout passes (the action timeout, 5 s, unless --timeout <ms>), then fails the step. A passing assertion records nothing, so it changes no verified transcript. The target is a CSS selector, or find as above: expect visible find role button --name Save --exact. The matcher comes first.

Two more are about the page rather than an element:

With --not, expect request holds when no finished request matches and none matching the URL (and --method, --type) is still in flight, since a late answer could still be the one you wanted absent: expect --not request "**/_api/v1/o/*" --failed is "every export was accepted", and it waits for the exports still on their way. --not same-document waits for a new document. A request that never finishes (a long poll) is never matched. A body is the request's own, as the page sent it: text is read as UTF-8, and a failure shows its size, never its text. Like every expect they record nothing.

A request the page starts while it unloads is not seen. A fetch (keepalive or not) or navigator.sendBeacon called from pagehide or visibilitychange reaches the server, but Chrome's DevTools protocol reports no request for it, so neither expect request nor network requests lists it (Playwright does not see it either). Assert on what the page sends while it is open, such as a batch flushed on a timer, and give expect request a --timeout longer than that delay. Leaving the page does not make such a request visible, and open about:blank is refused anyway.

set useragent "Mozilla/5.0 (X11; Linux x86_64) Chrome/130.0.0.0 Safari/537.36 telemetry-test"
open /
find role link click --name "Elastic Fundamentals"
expect url "**/get-started**"
expect same-document
expect --timeout 20000 request "**/_api/v1/o/l" --method POST --status 2xx
expect --not request "**/_api/v1/o/*" --larger-than 32kb
expect request "**/_api/v1/o/l" --body-contains '"docs-frontend"'

--not inverts any of them, and keeps checking until the matcher stops holding. --contains and --regex apply to text, value, attr, class, title and url; --ignore-case to text, attr and url. Only visible, hidden, attached and count can be asserted about an element that is not there; every other matcher needs one, even negated (--not enabled on a missing element keeps failing), as in Playwright.

expect visible find role heading --name "Your basket"
expect text #count "2 items"
expect --not visible .spinner
expect --timeout 10000 text "#status" "Done"
expect url "**/checkout"

A failure names what was expected and what the last check saw:

Journey stopped at journeys/shop.journey:9: expect text #count "3 items"
Timed out after 5s waiting for css #count to have text "3 items": received "2 items".

A regular expression is .NET's in cdp run and JavaScript's on Playwright; keep to the syntax they share, and quote it: unquoted, a backslash escapes the next character ('^\d+ items$'). There are no flags: use --ignore-case. $env:NAME works in an expected value and is redacted from messages. expect is ours: agent-browser has no assertions, so the export leaves these lines out.

These write files, only inside the artifacts folder the host chose (--artifacts, or JourneyOptions.ArtifactsDirectory); paths are relative to it and may not leave it. Without a folder they fail the step.