---
title: "ScriptBuilder Browser Extension Issues"
slug: "scriptbuilder-browser-extension"
updated: 2026-11-04T15:06:34Z
published: 2026-11-04T15:06:34Z
canonical: "success.panaya.com/scriptbuilder-browser-extension"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ScriptBuilder Browser Extension Issues

ScriptBuilder and Agent use a browser extension to record and play back web applications in Microsoft Edge or Google Chrome. The extension connection method is handled automatically, with no BiDi or extension-installation flags to configure.

For most users, **no extension setup is needed**. If your organization blocks extensions or requires managed browser sign-in, ScriptBuilder detects the relevant policy when you select **Record** or **Play** and displays an **Additional setup needed** dialog.

## What to check

- `ExtensionInstallBlocklist = *`: Ask IT to force-install the Panaya extension. If forced sign-in is not enabled, IT can alternatively allowlist it, after which you set up the Panaya user-data folder and install the extension manually.
- `BrowserSignin = 2`: In ScriptBuilder, go to **Main menu > Setup Panaya user-data folder** and complete the guided browser setup.
- **Both policies:** IT must add the extension to `ExtensionInstallForcelist`, and the user must set up the Panaya user-data folder. An Allowlist alone is not sufficient.

The dialog shows a checkmark for completed requirements and X for missing requirements. Follow the displayed instructions and retry Record or Play.

For the complete policy decision table, browser-specific extension IDs, setup steps, and escalation guidance, see the [ScriptBuilder Extension Policy – Troubleshooting Guide](/v1/docs/script-builder-browser-issue-troubleshooting-guide).

If the browser opens but the extension still cannot connect after setup, Panaya Support may recommend Chrome for Testing. If it is unavailable or does not resolve the issue, open a support ticket.

## Related

- [ScriptBuilder Setup](/script-builder-setup.md)
- [Registry Keys for ScriptBuilder Setup](/registry-keys-for-scriptbuilder-setup.md)
- [Browser Driver Version Mismatch](/browser-driver-version-mismatch.md)
- [DevTools Disabled by Policy](/devtools-disabled-by-policy.md)