Unable to use Practitest app using chrome extension

Resolved 💬 2 comments Opened May 29, 2026 by sivapoornima Closed Jun 1, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Title: Claude in Chrome regression: app.practitest.com and app.fullstory.com blocked after recent auto-update — worked yesterday

Body:

Summary

Navigation to app.practitest.com and app.fullstory.com is now blocked with "Navigation to this domain is not allowed" after a recent auto-update. Both domains worked as recently as yesterday / a few days ago.

What changed

The extension appears to have auto-updated. After the update, these domains now return a hard block instead of showing an approval prompt. No changes were made on my end.

Affected domains

  • app.practitest.com — blocked (was working)
  • app.fullstory.com — blocked (was working)

Working domains (same session, same extension)

  • helpdesk.partssource.com — still works fine

Expected behavior

Navigation should either work (as it did before the update) or show an approval prompt so the user can allow the domain.

Actual behavior

Hard block: "Navigation to this domain is not allowed" — no prompt appears, cannot approve.

Impact

  • app.practitest.com: Used for QA test case lookup during incident triage — searching test cases, pulling DB2 queries from test steps, verifying fix steps
  • app.fullstory.com: Used for session replay during incident triage — reviewing user sessions to diagnose issues

Environment

  • OS: Windows 11 Enterprise
  • Claude Code version: latest
  • Claude in Chrome extension: auto-updated (version unknown — chrome://extensions navigation also blocked)

Request

Please check what changed in the domain allowlist/blocklist in the last 24-48 hours and restore access to these two domains. Both are legitimate enterprise business tools used for incident management.

What Should Happen?

allow other websites to use chrome extension

Error Messages/Logs

Steps to Reproduce

Title: Claude in Chrome regression: app.practitest.com and app.fullstory.com blocked after recent auto-update — worked yesterday

Body:

Summary

Navigation to app.practitest.com and app.fullstory.com is now blocked with "Navigation to this domain is not allowed" after a recent auto-update. Both domains worked as recently as yesterday / a few days ago.

What changed

The extension appears to have auto-updated. After the update, these domains now return a hard block instead of showing an approval prompt. No changes were made on my end.

Affected domains

  • app.practitest.com — blocked (was working)
  • app.fullstory.com — blocked (was working)

Working domains (same session, same extension)

  • helpdesk.partssource.com — still works fine

Expected behavior

Navigation should either work (as it did before the update) or show an approval prompt so the user can allow the domain.

Actual behavior

Hard block: "Navigation to this domain is not allowed" — no prompt appears, cannot approve.

Impact

  • app.practitest.com: Used for QA test case lookup during incident triage — searching test cases, pulling DB2 queries from test steps, verifying fix steps
  • app.fullstory.com: Used for session replay during incident triage — reviewing user sessions to diagnose issues

Environment

  • OS: Windows 11 Enterprise
  • Claude Code version: latest
  • Claude in Chrome extension: auto-updated (version unknown — chrome://extensions navigation also blocked)

Request

Please check what changed in the domain allowlist/blocklist in the last 24-48 hours and restore access to these two domains. Both are legitimate enterprise business tools used for incident management.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

latest

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗