Skip to content

waitForChange

Wait until the UI has settled after your action. Use this instead of a fixed-duration wait when you’ve triggered an action (a new screen loads, content updates, a list scrolls) and want to block until the UI is quiet again. Returns immediately if the UI is already settled when this runs. Known limit: it cannot wait for a delayed async change that hasn’t started yet — for that, use a specific-element wait (e.g. assertVisible on the element you expect to appear).

Source

  • Kind: class-backed
  • Class: xyz.block.trailblaze.toolcalls.commands.WaitForChangeTrailblazeTool

Contract

  • Visible to LLM: yes (surface_to_llm: true)
  • Recordable: yes (is_recordable: true)
  • Host-only: no (requires_host: false)

Input schema

Optional parameters

  • timeoutMs — Integer Maximum time to wait for the screen to change, in milliseconds. Default 8000.
  • quietWindowMs — Integer Time with no further UI events required to consider the screen settled, in milliseconds. Default 300.
  • requireChange — Boolean When true, timing out with no change is an error. When false, a timeout is treated as a generous settle and succeeds. Default true.

Output

Returns: string (opaque text content)

Typed result schemas (kind: query | action, MCP structuredContent) are not yet carried by the resolved manifest — this section will gain detail when that lands.