Test a Tool on Your Site

Run a tool in the real browser context — on your actual site — before enabling it for AI agents.

Why test on the real site

executeJs runs in the visitor's browser and can interact with the DOM. A sandbox won't have your site's elements. Testing on the real page gives you accurate results.

Opening the test panel

Hover any tool card in the dashboard. Click the flask icon (🧪) to open the test panel.

If the tool has input parameters, you'll see a form to fill in test values.

Running the test

Fill in the arguments and click Open on site. This opens your site in a new tab with special query parameters:

https://yoursite.com?_aigentably_test=toolName&_aigentably_args=<base64>

The Aigentably snippet detects these parameters and runs the tool automatically.

Reading the result

A result overlay appears in the bottom-right corner of your site:

• Green (✓ Result) — the tool returned successfully
• Red (✗ Error) — the tool threw an error or returned { success: false }

The overlay shows the full return value as JSON and disappears after 15 seconds. Click × to dismiss early.

Common issues

"Tool not found on this page" The tool has a path pattern that doesn't match the current URL. Check your path pattern in the tool editor or try on a matching page.

Red overlay with DOM error The executeJs code couldn't find an element. Check your selectors in the browser DevTools on the actual page first.

Test calls don't appear in analytics Expected — test mode is intentionally excluded from analytics to keep your data clean.