Using Browser Click Automation

Use click to activate links, buttons, and interactive UI elements. Prefer click for most cases; switch to Hardware Click only when a site requires a real, trusted gesture (e.g., OAuth popups).

Command fields

• selector (CSS or Playwright-like: text=..., role=..., xpath=...)
• xpath, text, role (fallbacks if selector omitted)
• exact (boolean), button (left|middle|right), click_count (number)
• modifiers (CSV: Alt,Control,Meta,Shift), scroll_into_view (boolean, default true)
• trusted (boolean) — simulate hardware click via CDP
• Attribute helpers: placeholder, aria_label, input_type, name_attr, attr_contains, nth (0-based)

Examples

Click by visible text (exact):

{
  "command": "click",
  "selector": "text=Start a post",
  "exact": true
}

3rd matching button by ARIA label:

{
  "command": "click",
  "aria_label": "Add to cart",
  "nth": 2
}

Trusted click for OAuth button:

{
  "command": "click",
  "selector": "button.gsi-material-button",
  "trusted": true
}

With key modifiers:

{
  "command": "click",
  "selector": "a.product-tile",
  "modifiers": "Meta,Shift"
}

Tips

• Prefer selector; runner normalizes text=, role=, xpath=.
• Keep scroll_into_view on to reduce “not clickable” errors.
• Use nth to disambiguate repeated elements.
• Reserve trusted for sites that require real user gestures.

Troubleshooting

• Nothing happens: Add wait_for_selector (state: "visible") before click.
• Wrong element: Use exact: true or attribute helpers.
• Popup didn’t open: Use trusted: true, then wait_for_navigation or wait_for_selector in the new tab.