assertVisible

Assert an element is visible on screen by its ref ID from the snapshot. Use the short hash ref shown in square brackets (e.g., y778 from [y778] “Network & internet”). These refs are stable across captures of the same screen. Optionally pass expectedText to also verify the element’s rendered text — use it whenever the case asks to verify a specific value (e.g. “verify the checkout button shows $5.00”, “expect status to be Active”) instead of just confirming the element exists.

Source

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

Contract

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

Input schema

Required parameters

• ref — String The element ref from the snapshot (e.g., ‘y778’)

Optional parameters

• expectedText — String Optional. When set, asserts the resolved element’s rendered text equals this value after whitespace trimming (case-sensitive). Pass the stable rendered text verbatim — e.g. “Charge $5.00”, not “the checkout button”. Exclude volatile state that changes run-to-run (live item counts like “3 items”, timestamps, quantities); pin only the part that stays constant. Leave null when only the element’s presence matters.
• reasoning — String

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.