Why Ai2 Playground Shows “Please Enable JavaScript to Run This App”

The message appears because playground.allenai.org is a JavaScript-rendered web application: the page you receive from the server is essentially an empty shell, and the interface, models, and tools are all built in the browser by JavaScript. If JavaScript is disabled, blocked, or fails to execute, the app never loads and you see only the “Please enable JavaScript to run this app” notice. The fix is to enable JavaScript for the site, use a modern browser, and turn off script blockers for that domain, then reload.

What the message actually means

The visible page evidence for playground.allenai.org contains only this single line: “Please enable JavaScript to run this app.” There is no server-rendered content behind it — no menu, no model list, no fallback text. That is the signature of a client-side application, where the HTML is a container and everything else is assembled by scripts after the page loads.

So the message is not an error from a broken feature. It is the app telling you it could not start at all. Two common causes:

• JavaScript is turned off in the browser settings, so no script runs.
• JavaScript is on but blocked for this site — by an extension, a content blocker, a corporate policy, or a privacy setting — so the scripts are refused or stripped.

Steps to get the app to load

1. Check that JavaScript is enabled. In Chrome, Edge, or Firefox, open the browser settings, search for “JavaScript,” and confirm it is allowed for all sites (or at least not blocked for playground.allenai.org). In Safari, check Settings → Security → Enable JavaScript.
2. Use a current browser version. The app depends on modern JavaScript features; an outdated browser may fail silently. Update Chrome, Edge, Firefox, or Safari to the latest release and try again.
3. Disable script blockers for this domain. Ad blockers, tracker blockers, and privacy extensions can block the scripts the app needs. Turn them off for playground.allenai.org, or add it to the allowlist, then reload.
4. Try a private/incognito window with extensions off. This isolates whether an extension is the cause. If the app loads there, re-enable extensions one at a time to find the culprit.
5. Reload with a hard refresh. A cached, partially loaded version can leave you stuck on the notice. Use Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac) to bypass the cache.

Expected result: the notice disappears and the Playground interface renders — model selection, input area, and output panel.

If the page is still blank after enabling JavaScript

Work through these in order, since each rules out a different layer:

• Network or firewall restrictions. Corporate networks, school filters, and some regional blocks can prevent the app’s scripts from loading. Try a different network to confirm.
• Browser policy settings. Managed devices can disable JavaScript or restrict script sources via administrator policy. Check with whoever manages the device.
• Strict privacy modes. Some browsers’ strict tracking protection blocks third-party scripts the app relies on. Lower the setting for this site.
• Conflicting extensions. Two blockers can interfere even if each is individually allowlisted; test with all extensions disabled.

If the notice persists across a modern browser, a clean profile, and a different network, the problem is likely on the service side rather than your browser — in that case, retry later rather than changing more settings.

Quick reference

The key point: this message is a startup gate, not a content error. Once JavaScript runs for the domain, the Playground app itself loads and the notice is gone.