Get
Help

Self-healing

Our 8-tier fallback chain (id → data-testid → position → aria-label → text → similar text → toggle-label → class) handles layout changes automatically.

AI features

AI Decision steps, AI-generated values, and AI-driven clicks use your own OpenAI key or our authenticated backend when signed in.

The debugger banner

Why Chrome shows a banner during trusted-input replay, and why it can't be hidden — it's Chrome's security requirement for chrome.debugger.

Background execution

Runs continue while the browser is minimized or the tab is unfocused. We persist run state to survive service-worker termination.

Data extraction

Extract text, attributes, or table data during runs and export results as CSV/JSON.

Alerts

Chrome notifications, email, Telegram, and WhatsApp alerts when a run finishes or needs attention (dispatched by our backend when signed in).

Steps to reproduce

What you recorded, and what happened when you ran it. Include the URL if it's not sensitive.

The run log

The Runs tab shows exactly which fallback tier matched, or why a step failed — copy it in. Screenshots help too.

Chrome version

chrome://version — especially relevant for anything touching the debugger/CDP path.

Extension version

Check More → Settings in the side panel for the current version number.

Sync problems

If workflows aren't syncing, check that you're actually signed in and the extension has internet access. Refresh the side panel after signing in.

Offline operation

Recording and replay work fully offline. Only sync and backend-dispatched alerts require an internet connection.

Account deletion

Delete your account and all synced data from the dashboard. This removes everything from our servers but not your local extension storage.