[BUG] Claude in Chrome: app.respond.io blocked by server-side domain classifier

Resolved 💬 2 comments Opened Apr 13, 2026 by michael-laps Closed Apr 16, 2026

Description

The Claude in Chrome extension blocks all interactions with app.respond.io — a legitimate business SaaS platform for customer messaging and WhatsApp automation.

All tools fail:

  • navigate → "Navigation to this domain is not allowed"
  • read_page → "Permission denied for reading pages on this domain"
  • computer (screenshot) → "Permission denied for this action on this domain"
  • find → "Permission denied for reading pages on this domain"
  • get_page_text → "Permission denied for reading page content on this domain"

Configuration

  • Organization settings (claude.ai): "Allow extension" is selected, Blocked sites list is empty
  • Extension settings: No domain restrictions configured
  • Chrome site permissions: All default (no blocking)

Context

  • This domain was accessible approximately 1 week ago (early April 2026) and stopped working without any user-side configuration change
  • app.respond.io is a business messaging platform (similar to Intercom/Zendesk) used for WhatsApp Business automation
  • We use it alongside HubSpot CRM and Make.com for sales pipeline automation — HubSpot (app-na2.hubspot.com) works fine with the extension
  • This is blocking legitimate business workflow automation (creating WhatsApp message templates, building messaging workflows)

Expected Behavior

app.respond.io should be accessible like any other business SaaS platform (HubSpot, ClickUp, etc.)

Environment

  • Chrome on macOS (Darwin 25.4.0)
  • Claude in Chrome extension (latest version)
  • Organization: leeladevs.com

Related Issues

  • #43255 — Main tracker for "Navigation to this domain is not allowed"
  • #40173 — Server-side domain blocking breaks business automation

View original on GitHub ↗

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